85% say the bottleneck is reviewing AI code, not writing it. @gitlab asked…

85% say the bottleneck is reviewing AI code, not writing it. @gitlab asked 1,528 developers and buyers. The queue moved from generation to validation. @SonarSource's 1,100+ survey says 42% of committed code is AI-generated. 96% do not fully trust it is functionally correct. Only 48% always check before they commit. We generate faster than anyone can read. Another round of doubt will not shrink that queue. @unclebobmartin ships unread agent code. He can, because the checks fail it without him: > Unit tests he never reads > Acceptance tests he spot-checks > Mutation on the suite > Quality metrics on the output The transferable part is not his full stack. It is how much autonomy a change earns when something cheap can fail it. Reading every line just makes you the new queue. > When can a change ship unread? > What still needs a name on it if it ships wrong? > What fails if nobody reads the diff? Full Breakdown ↓↓