The headline numbers on AI-assisted coding are genuinely impressive, and they are also incomplete. VentureBeat, drawing on Faros AI data and Google's DORA research, reports task throughput per developer up 33.7% and PR merge rates up 16.2% — but the incidents-to-PR ratio has risen 242.7% and bugs per developer are up 54%. More code is shipping; more of it is breaking. The 'software factory' framing assumes the factory has quality control, and the data suggests that, on average, it does not.
Sitting alongside that quality picture is a cost picture that most finance teams have not modelled. CIO Dive reports Gartner's projection that consumption-based AI coding costs will exceed the average developer salary by 2028, with ungoverned autonomous agent usage already depleting budgets faster than planned. The economic argument for AI in engineering has quietly shifted from 'cheaper than developers' to 'potentially more expensive than developers, if you don't govern it' — a very different conversation about ROI and vendor transparency.
Ford offers a real-world cautionary note. The Verge reports that the company had to rehire former engineers to correct mistakes introduced by its automated engineering systems — and went on to take its first No. 1 JD Power initial quality ranking in 16 years. The recovery story is encouraging; the underlying lesson is sobering. Institutional knowledge that was removed had to be brought back at cost, and the quality dip happened inside processes leaders presumably believed were under control.
Underneath all three data points is a broader argument, captured in The AI Optimist's framing: as AI drives the cost of execution toward zero, code itself stops being a moat. What endures — proprietary data, trust, relationships, culture — is precisely what gets eroded when AI-driven output ships faster than quality and cost can be governed. The competitive question is shifting from how much AI you've deployed to how well you can vouch for what it produced.