Do lines of code measure developer productivity?
Core argument: Kedrosky argues an 8x increase in software lines of code generally corresponds to a far smaller increase in actual engineering throughput, since AI agents generate boilerplate, wrappers, tests, and what-if code at near-zero cost.
[Kedrosky warns a new Anthropic paper based on internal data on increased developer productivity, as measured by software lines of code (SLOC) per developer measures output, not value]. Ten thousand lines of generated code are often less valuable than deleting a thousand lines of technical debt. SLOC as a measure rewards quantity, not usefulness. AI systematically inflates the metric. Agents generate boilerplate, wrappers, tests, and what-if code at near-zero cost. An 8x increase in SLOC generally corresponds to a far smaller increase in actual engineering throughput. Code volume creates liabilities. More code means more maintenance, complexity, attack surface, and debugging load. The best engineers create value by writing less code, not more. Most evidence is about implementation, not automating research. The strongest results involve coding, experiment execution, and debugging. Recursive self-improvement depends on solving an unsolved problem.

