The dream today is that agents might prefer your website due to it's MCP and actually purchase something. i.e. 'hey claude go find me the cheapest places I can buy these headphones'

Honestly if you're launching a new model, you should probably just make it free for the 24 hours after launch so people can test it out. Otherwise just wait till it's on openrouter.

[1] https://press.stripe.com/the-making-of-prince-of-persia

It's so much more annoying to go drag boxes around and type out little JS snippits in every chart as opposed to just telling claude to make the chart.

But your landing page + video was just slop city. Removes 100% of credibility for me.

I know the advice is launch early and often, but honestly I would just point people to the github until you have something better.

Occasionally I see real security researchers on HN complaining that no one takes the disclosure seriously, or that people reply immediately with a cease and desist. But from the receiving end it's just because the spam is unmanageable.

Even in this one, they just report that OlmOCRBench and OmniDocBench have "known limitations" and that's why they report flagship numbers from their internal benchmark.

https://getomni.ai/blog/benchmarking-open-source-models-for-...

[1] https://news.ycombinator.com/item?id=48616086

That's usually things like caltrain / muni. But I would definitely sponsor a $300/mo waymo subscription if it was like 20 rides a month.

- CDs moving to Mp3s moving to the ipod and finally streaming

- Games moving from 8bit to early 3d graphics to where they are today

- Family computer moving to laptops and eventually to ipads

- Landlines to early cell phones to the iphone today

All of these experiences helped ground the core principals behind this technology. And the pace of these transformations (while rapid) was still something you could keep up with. Everything was built on the same principals.

But today kids go from zero to iPad + AI generated tiktoks by time they turn 2. Sure parents can try to hide the tech, but it doesn't change the fact that it's out there and available as soon as they enter school.

Maybe I'm overindexing on my childhood, but I would love to recreate some abridged history of this for my kids. I think seeing the building blocks helps build a much more healthy relationship with technology.

And let's say that work is correlated with quality. Company A wants to spend 10x less time working, while Company B works 10x more. Company B therefore has a better product than Company A, so eventually Company A goes away. The consumer still consumed the same amount, but they switched to the better product.

In the world where someone can take your cake by working 25% more hours, it's always going to happen.

I think this sentiment applies well to junior software engineers (with mentorship). But imagine the much larger swaths of entry level employees in operations, support, or sales functions. When you have a 400 person team with 20% annual turnover (since people move in / out of entry level jobs frequently), the management + training + monitoring becomes a huge challenge.

I think the typical HN sentiment of "llms aren't deterministic" fails to take into account how non-deterministic giant groups of people are. Every group of 10 people typically needs a manager. And every 10 managers needs another manager. By comparison the engineering work on dialing in your LLM guardrails feels pretty worthwhile.

https://www.construction-physics.com/p/do-us-ports-need-more...

And I wasn't attached to that complex implementation in the way I would be if I architected it from scratch, so it was easy to move on.

But! Because of AI I was able to rapidly hack out like 4 variants of this feature that I didn't like. And felt comfortable throwing them away just as quick.