This seems entirely backwards. Why spend money to optimize something that _isn't_ the bottleneck?

My team is incredibly clueless and complacent. I can't even get them to use TypeScript or to migrate from Yarn v1.

I don't see how that would change if you accept the premise that code is now a commodity.

Some recent techniques claim to be solving this problem but none reached a release yet.

Working with what we have now, this is a recipe for disaster. Agents often lies about the outputs. The shorter the context space they have to manage while the bigger the data already in context makes it prone to lie and deceive.

It works ok for small changes on top of human code. That's what we know works now. The rest is more yet to be reached

Plan before you code. Now your plan is just in a prompt.

For this, which summarises vibe coding and hence the rest of the article, the models aren't good enough yet for novel applications.

With current models and assuming your engineers are of a reasonable level of experience, for now it seems to result in either greatly reduced velocity and higher costs, or worse outcomes.

One course correction in terms of planned process, because the model missed an obvious implication or statement, can save days of churning.

The math only really has a chance to work if you reduce your spend on in-house talent to compensate, and your product sits on a well-trodden path.

In terms of capability we're still at "could you easily outsource this particular project, low touch, to your typical software farm?"