If you thought the speed of writing code was your problem - you have bigger problems
Summary
Andrew Murphy argues that boosting code output with AI tools often worsens delivery because bottlenecks lie in the value stream, not coding speed. Drawing on Goldratt's Theory of Constraints, the piece highlights five bottlenecks: not knowing what to build, work after code is done, deploy trust, shipping outcomes, and calendar bottlenecks. It prescribes unsexy but practical steps: map the value stream, measure cycle time (not output), remove wait states, stop starting and start finishing, and engage with the people doing the work to reduce cycle time and improve actual shipping velocity.