Christian Bird on why more code has not meant faster shipping

Bird's 21-minute talk argues that AI tools raised the volume of work started without a matching rise in what ships. We read the 19-page handout, not the recording. One slide, citing an NBER working paper by Demirer, Musolff and Yang covering more than 500,000 GitHub developers using autonomous coding agents, sets a 240% rise in commits against a 30% rise in actual releases.

Much of the talk draws on a 30-interview study of engineers, managers and PMs on long-lived products, which the handout lists as in submission. One participant says: "If you can do the code in one day, you're still talking 30 days before it actually gets deployed." A senior engineer says: "The pace at which we have to review is fast outpacing our ability to review." The talk names the result "Systemic Conversion Strain": the cost of generating code fell while the cost of shipping it barely moved, and expectations treated the two as the same. The handout closes with three recommendations: "scale verification with generation", "count outcomes, not activity" and "protect the people who ship things".

Why it matters: If your factory reports commits or merged PRs, it is reporting input. Bird's case is that review, integration and deployment set the pace. Review is the step the paper above tests handing to an agent. The interview study has not been published, so its quotes should be read as early findings shown in a talk.