The idea that the entire top down processes of a business can be typed into an AI model and out comes a result is again, a specific type of tech person ideology that sees the idea of humanity as an unfortunate annoyance in the process of delivering a business. The rest of the world see's it the other way round.

I agree with you that OpenAI seems much more risky in terms of it's actual true viability as a business, but the risk:reward must be there for Softbank.

This is sell-side idealist thinking and blurred view of reality. We're not approaching it, we're not even seeing metrics to suggest that any sub-division of any business is making serious progress there at all.

Too many people are hyping something that will not happen in our lifetimes and we risk looking beyond the terrible state of large global economies, poor business practice and human exploitation on mass scales to a place we will never see. It's more fun to try and shape future possibilities for large profit that we'll probably never have to justify, than attempt to deal with current realities, and thus go against the grain of investment trends today, for an uncertain benefit.

Far too many smart people are putting their energies into such discussions that add a lot of drag to the process of society and humanity moving forward for no net gain at all.

This seems like a typical engineer forgets people aren't machines line of thinking.

I can't believe so many replies are struggling with the easy answer: privacy, security, "local first", "open source", "distributed", "open format" etc etc etc are developer goals projected onto a majority cohort of people who have never, and will never, care and yet hold all the potential revenue you need.

One thing I did notice though from looking through the examples is this:

Uncaught errors automatically cause retries of tasks using your settings. Plus there are helpers for granular retrying inside your tasks.

This feels like one of those gotchas that is absolutely prone to benign refactoring causing huge screwups, or at least someone will find they pinged a pay for service 50x by accident without realising.

ergonomics like your helper of await retry.onThrow feel like a developer friendly default "safe" approach rather than just an optional helper, though granted it's not as magic feeling when you're trying convert eyeballs into users.

What it isn't is the actual final "thing" itself. It's just the thin veneer right now.

I'm not convinced that that revolution was worth whatever trillions we'll end up spending, but fortunately that's not on my shoulders to be worried about.

Editing this kind of configuration has far less cognitive load and loading time, so distractions aren't as destructive to the task as they are when coding. You can then also structure time so that productive agent coding can be happening while you're doing business critical tasks like meetings / calls etc.

I do think this is overkill though, and it's a bad plan and far too early to try and formalize The One Way To Instruct AI How To Code, but every advance is an opportunity to gain career traction so fair play.