Overview
A new argument is gaining traction in software engineering circles: the productivity gains from AI coding agents are unsustainable unless those same tools also reduce maintenance costs. The core claim is straightforward — if an AI doubles your code output but the resulting code is twice as hard to maintain, your net productivity gain is zero, and within months you may be worse off than before.
The math behind the claim
The argument rests on a simple model of software maintenance. Every line of code written incurs ongoing costs: bug fixes, cleanup, dependency upgrades. For each month spent writing code, a developer will spend some amount of time in subsequent years maintaining that code. A crowd-sourced estimate from 50 developers suggests roughly 10 days of maintenance per month of new code in the first year, and 5 days per year thereafter.
Under this model, a team starting a new project spends the first month entirely on new features. By month 30, more than half their time goes to maintenance. After ten years, nearly all capacity is consumed by upkeep.
The AI multiplier problem
Introducing an AI coding agent that doubles output changes the equation — but not necessarily for the better. If the agent produces code that is twice as hard to maintain as human-written code, the maintenance burden quadruples (2x output × 2x maintenance cost per unit). According to the model, productivity returns to baseline after about five months, and then continues to decline below where it would have been without the AI.
Even if the AI produces code with identical maintainability, the productivity gains are temporary. Doubling output while holding maintenance costs steady still doubles the absolute maintenance burden. Over time, that burden consumes the initial speed advantage.
The required inversion
For AI coding tools to provide lasting benefit, the argument states that maintenance costs must decrease in inverse proportion to the speed increase. If you produce twice as much code, each unit of code must cost half as much to maintain. Three times the output requires one-third the maintenance cost. Without this inversion, the team is trading a temporary speed boost for permanent indenture.
Practical implications
The argument does not claim that AI coding agents are inherently bad. It identifies a specific condition for their sustainable use: the tools must actively reduce maintenance costs, not just accelerate code production. This could happen through better code quality, automated refactoring, improved test coverage, or AI-assisted debugging and dependency management.
Currently, there is little evidence that mainstream coding agents significantly reduce maintenance costs. Most reported gains are in initial code generation speed. The model suggests that teams adopting AI for coding should invest equal effort in tools and practices that lower the long-term cost of maintaining that code.
Bottom line
The message is practical: measure your maintenance costs before and after adopting AI coding tools. If your output increases but your maintenance burden grows proportionally, the productivity gains will not last. The goal is not just faster code writing, but code that is cheaper to maintain over its lifetime.