lbhdc

In my career transition I learned and grew a lot, and it helped give me a different perspective on some problems.

I do wonder if people changed their careers every 10-15 years if they would be happier. You would get to work on a whole different set of problems, you would get to learn new skills, and eventually demonstrate your mastery over those new skills.

https://www.theverge.com/2024/7/26/24206969/google-pixel-9-a...

Kind of like a plan that starts with "first make a viral youtube video then...". That first step is significantly larger and more difficult than it seems, and kind of sounds like that is your experience.

If I were in your situation, I would prioritize the quickest path to stability. If your e-commerce business is popping off, drop the startup. If neither of those are going anywhere, get a job. Without having some stability it will be difficult to take another swing at your startup.

Once you are treading water again, I would re-evaluate your startup strategy. I wouldn't write any code, or build any prototypes yet. First step is getting in front of people who are your target users and ask them lots of questions about their problems. If the idea you are showing them isn't doing it, ask about their other problems. Build the lowest effort thing that solves that problem in the happiest case and keep showing it.

https://viewport-tester.com

The detailed text on the modal says: We can only load URLs that pass standard pattern checks.

I noticed another possible bug. When trying it out on your website, it reports an "Invalid URL" error.

TFA mentions this hasn't been the case.

Some things that have were notable:

Model pipelines tend to be flakier than other pipelines you have. They are much more complicated, and it can be easy to hit a resource limit if you aren't careful, or have a unhandled exception accidentally kill a pipeline 10hrs into it.

Avoiding those outright is obviously the best path, but that can be easier said than done.

One thing that we found really helpful was creating an error record in a database for every piece of data that failed to get processed, where it failed in the pipeline, etc. Retries, and alters were easy to tack on after that.

Kubeflow is the one I see used the most (self hosted). The public clouds also have products targeting these workloads.

Ad tech

How did you develop and launch it?

New features for an existing product. Most of them were switched on globally when we launched them.

Which LLM(s) are you using (e.g. GPT-4, Claude, open source models)?

We started using language models before ChatGPT and friends came out. We built our models from scratch, and still use and update them.

What's your revenue model?

Saas

How much are you making (if you want to share, ballpark figures are fine)?

We don't charge extra for features that use ML, it's an implementation detail that our users don't care about. So, I am not sure what % of the whole they contribute to. Its not the majority.

What challenges have you faced?

"mlops" was a real challenge in the early days, and we built so many bespoke distributed systems to figure it out. Eventually we did, but finding the right balance between building a performant system and a system that doesn't explode in cost was tough. There is off the shelf things that do this these days, but they can be expensive.

Any advice for others looking to enter this space?

Solve problems customers are willing to pay for. Some of the features we have dreamed up have been total flops. Many of the features we have developed (ml or otherwise), while the add value for the customer and add to the moat, they aren't valuable enough that our users are willing to pay extra for it as a standalone product.

    auto get_x/(a, b)(const int^/a x, const int^/b y) -> const int^/a {
      return x;
    }

    template<class T+, class E+>
    choice expected {
      [[safety::unwrap]] ok(T),
      err(E);
    
      T unwrap(self) noexcept safe {
        return match(self) -> T {
          .ok(t)  => rel t;
          .err(e) => panic("{} is err".format(expected~string));
        };
      }
    };

As someone who likes heavy keyboard centric flows, but still likes using a mouse, gnome feels like it was made with me in mind.

The keyboard navigation in the overview feels just as good as it does with a mouse.

The link OP shared is open to the public to me. https://staging.us.coca-cola.com/products/coca-cola-energy/c...

I would think that even if these weren't showing up on google that people would be able to find the subdomains through dns. They should probably move these to an internal domain so they are harder to find.

Looking at the drone war in Ukraine there is an intense battle to disrupt control signals to drones. If the drone can drive it self and take action without input, the effectiveness of signal jamming becomes much more reduced.

It throws an error when its full screen though. There is more to the error, but it wont let me copy it.

    indexDB.databases is not a function.

https://news.ycombinator.com/item?id=40172033

I saw a saas recently that has something targetting this. They will automatically update your robot.txt to include different crawlers they find.

This will only stop crawlers that obey robots.txt though.

I own an xbox (previous generation), and pay for game pass. There hasn't been a game on game pass or that has come to the store (that I am interested in) that doesn't play on the previous generation. I _want_ a new one, but haven't bumped up against anything that I haven't been able to do with my older xbox, so I haven't had anything to look forward to or get access to with the new system.

I also wonder how much their naming scheme hinders their sales. I find it so confusing, and the current and previous generations may as well have the same names as I can't disambiguate them.

The first monorepo I worked in was a python/typescript monorepo. It largely grew organically, and was heavily iterated on. We had no tooling to manage the complexity, and constant bumped into sharp edges that made life difficult.

    - Dependencies change and silently break applications or developer environments.
    - Figuring out how to start up applications you didn't work on could be difficult because you needed to figure out the tool chains and how to invoke them. This painpoint came up everytime toolchains changed.
    - Figuring out where dependencies were used was really hard. This lead to lots of zombie code, we weren't sure if it was alive or dead.

With that being said, bazel does seem to solve most of the sharp edges we had with our ad-hoc/no tooling, but it comes at a cost. Bazel is not trivial, and won't allow you to do some things that the underlying toolchain might have been okay with. So that may leave you making code changes to fit inside bazels constraints.

Bazel tooling also isn't equally mature across all languages. The go tooling is pretty mature, and there are great generators that 'make things work', the situation for frontend is less mature, but getting better. It will add additional friction that webdevs might not love.

At the end of the day though, I would choose to use something like bazel (or one of the alternates), and the friction it brings over not having it.

Example bazel frontend. https://github.com/bazelbuild/examples/tree/main/frontend/ne...