Quoting James Shore

Shore's framing quietly shifts accountability onto vendors: if productivity claims are real, the maintenance cost curve should be measurable and contractually defensible, yet no major AI coding tool provider currently publishes anything resembling a maintenance-burden metric alongside their velocity benchmarks.

This is largely disconnected from recent activity in our archive, as we have no prior coverage to anchor it to. It belongs to a growing but still underreported conversation about the second-order costs of AI-assisted development, a space where the dominant public discourse has been almost entirely captured by lines-of-code and time-to-ship metrics. The argument Shore is making has been circulating in engineering leadership circles for months, but it rarely surfaces in vendor positioning because it introduces a liability framing that cuts against the clean productivity story most AI coding tools are selling.

Watch whether any enterprise-focused coding agent vendor (GitHub, Cursor, or the major cloud providers) introduces a maintenance or defect-rate metric into their official benchmarks within the next two quarters. If they do not, Shore's critique will have identified a durable blind spot in how the category measures itself.