Agree, it’s not the graph representation that’s valuable, it’s the attribution and business logic of the workflows themselves. The concrete values and weights that go into making these deterministic decisions.
I still think is the angle they are after. Get these things locked down, and then force through the lockdowns with their endless cash. Otherwise, their market becomes commodified with plentiful competitors. It’s a strategy to create an oligopoly.
I’m a fan for sure but everything is said is true. If the products were bad I’d say that. The majority of people here at the complete opposite and exist to dump on Elon related companies for no reason other than they don’t like him personally.
Most people who comment positively on AI are either shills or people working in the AI industry (gotta keep the bubble expanding). The OP experience matches mine with most models for any kind of serious work. In fact, it was the reason why Claude was previously successful because it was the most railed model.
I've tried the latest models across OpenAI, Claude, Chinese, etc. They just do stuff. That's not how work is though. You want them to do specific work, at which point it's a real hassle to follow up on all the garbage they have been outputting.
I think it would work well as a multi-emoji compiler too. Some phrases pair well with N emojis, and you’d be able to produce arbitrarily many emojis per phrase
Who makes assumptions about how others do things in 2026? Line breaks are apparently relevant, review agents complain about them, soft breaks are super annoying for vim motion users, opinions are still like ani
If line breaks really were irrelevant, the author wouldn't have felt the need to give a tip all around optimising line breaks.
Personally, I would have hoped by 2026 we had better IDE's and tools for managing code in text files such that developers with different preferences for a number of characters in a column or things like how you display comments can be accommodated. Yet still teams end up arguing about what standard to use.
This is a bit like vim vs Emacs - everyone should be able to use their favorite setup, and the formatting should not get in the way of the engineer's preferences.
reply