An AI coding agent, used to write code, needs to reduce your maintenance costs
Scored daily by a customisable AI persona to surface the most relevant engineering leadership news.
Focused on AI coding agent maintenance, directly matches reader interests.
James Shore argues that AI coding agents must proportionally reduce long-term maintenance costs to avoid overwhelming teams with debt. Using Wisdom of the Crowd estimates (10 days maintenance per month of code in year one, 5 per year thereafter), he shows that 2x code output without halving maintenance leads to a faster productivity cliff. Developers who skim or approve PRs blindly—the "Rock Lobster" scenario—compound the risk, trading short-term speed for permanent indenture.
- Measure and enforce maintenance cost reductions every time you adopt an AI tool, or you'll accumulate debt faster than you can pay it down.
For a senior engineer evaluating agentic coding tools, this reframes the productivity debate: velocity without proportional maintenance reduction (e.g., via test coverage, refactoring, or architecture) creates a permanent drag that undermines long-term developer effectiveness.