Somewhere in the last two years, writing code quietly stopped being the expensive part of software. An AI assistant can produce a working feature in an afternoon and a plausible product in a week. What it cannot do is know whether either of them should exist.
Here is the part the industry is still catching up to: typing was never the bottleneck. The slow, expensive work of building software has always been the deciding — what the data model claims about your business, where the boundaries sit, which features to refuse, what happens when a payment fails halfway through. The cost of producing code has collapsed. The cost of a wrong decision has not moved at all.
What the demos don't show
AI-generated code has a particular character: it is confident, fluent and optimised to look correct. It handles the happy path beautifully, because the happy path is what it was asked for. The edge cases — the cancelled subscription, the duplicate webhook, the user who belongs to two organisations — were never in the prompt, and they are precisely where products live or die. The distance between an impressive demo and software you can bill customers on is not the last 20% of the work; it is a different kind of work.
There is a quieter problem too. When code is cheap, far more of it gets produced — which moves the bottleneck to reviewing and verifying it. A team that generates ten times the code without ten times the scrutiny has not sped up. It has automated the production of its own risk.
Where judgment earns its keep
Watch what a senior engineer actually does with these tools and the value becomes obvious. They frame the problem before generating anything. They reject the plausible-but-wrong answer because they have seen where it leads. They hold the line on the data model and the architecture, because those decisions outlive every generated function. In experienced hands, AI is genuine leverage — the same judgment, applied faster.
In inexperienced hands it is leverage too, just pointed the other way: a bad decision has never been cheaper to mass-produce.
What you are paying a development team for was never lines of code — it was always knowing which lines should exist, and standing behind them when reality pushes back. That has not changed; it has concentrated. Teams that pair machine speed with senior judgment now ship faster and sounder than either could alone. Teams that adopt the speed without the judgment ship their mistakes at machine speed — and the market is about to run that experiment at scale.