The agent wrote it in an hour. Who maintains it for six years?

Agents made code nearly free to write. They didn’t make it free to own. Every month of new code still carries years of upkeep, and doubling the output without cutting the upkeep turns a speedup into a standing bill. This week we look at what stays expensive when code gets cheap, and why the new, good software hasn’t shown up yet.

• THE BILL · James Shore
  You Need AI That Reduces Maintenance Costs (opens in a new tab) · every month of code costs about ten days of upkeep in its first year and five a year after that, so an agent that doubles output without halving upkeep turns a speedup into a permanent penalty
• THE CURVE · Chris at Entropic Thoughts
  The geometric model of maintenance (opens in a new tab) · fits upkeep curves to eight real projects, from tmux to Rust, and finds the cost fades instead of compounding: about three hours of upkeep for every hour of new work, spread over roughly six years
• THE LONG WAY · Dan Cohen
  The Slow Formation of Durable Software (opens in a new tab) · Zotero took five years to reach a prototype because its team didn’t yet know what it wanted, and no prompt can encode a vision nobody has yet
• SCARCITY · Gustavo Pezzi
  Can Ease of Creation Lead to Decrease in Quality & Value? (opens in a new tab) · when making things gets cheap, quality falls, and what stays scarce is taste, understanding, care for details and trust
• THE PUZZLE · Nate Meyvis
  Where is all the new, good software? (opens in a new tab) · nine conjectures, some of which he admits carry little weight, on why cheap code hasn’t visibly made software better