Post #3309409

2026-06-13 13:28 UTC

This is by an llm-boosting firm, so be aware that it’ll have a lot of marketing in it. It doesn’t say nice things about vibe code (presumably because the authors want to sell you a solution) but the numbers are interesting even so. faros.ai/…/ai-acceleration-whiplash-takeaways A few choice snippets, none of which will surprise anyone here: For every code change merged, the probability of a production incident has more than tripled. The incidents-to-PR ratio is up 242.7% as teams move from low to high AI adoption. Bugs are accelerating, not stabilizing. In our 2025 AI engineering report on the AI Productivity Paradox, bugs per developer were up 9% as AI adoption grew. In this dataset, that figure has risen to 54% The most experienced people in your organization are being buried. Median time to first PR review is up 156.6%. Average time spent in code review is up 199.6%. Median time in review is up 441.5%. The engineers with the deepest knowledge of the system are spending their most valuable hours unraveling plausible-looking code that should never have reached them in the state it did.

Replies (1)

@YourNetworkIsHaunted@awful.systems 2026-06-14 05:55

This is fascinating to me and has shades of Iris Merideth’s The Problem is Culture. In other engineering fields, if you had a tool that cut costs but caused a threefold increase in failures you would be looking at a massive scandal, probably because if this was structural engineering rather than software engineering you’d be looking at a new Grenfell Tower or Hyatt Regency Walkway from every other project that used this shit. From what I’ve been following I don’t know that vibe coding has directly racked up quite so literal a body count yet, but if this pattern holds (and I see no reason to expect otherwise) then it’s only a matter of time before someone fucks up something important. Also the fact that the framing here doesn’t seem to treat this as an existential risk to the project of AI coding is fascinating. If you’re not producing stable and secure applications in prod then what in the actual fuck are you writing all that code for?

Open ##3314457