New blog:

I’ll get straight to the point: your AI coding agent, the one you use to write code, needs to reduce your maintenance costs. Not by a little bit, either. You write code twice as quick now? Better hope you’ve halved your maintenance costs. Three times as productive? One third the maintenance costs. Otherwise, you’re screwed. You’re trading a temporary speed boost for permanent indenture.

Oh, you want to know *why?* Sure. Let’s go for a drive.

https://www.jamesshore.com/v2/blog/2026/you-need-ai-that-reduces-your-maintenance-costs

James Shore: You Need AI That Reduces Maintenance Costs

@jamesshore This is interesting. In other words, are we moving the bottleneck from programming to maintenance?

https://mastodon.green/@timolaine/116517597532725227

Timo Laine (he/him) (@[email protected])

"When we deploy a digital tool like email to speed up communication, or generative AI to create (sloppy) slide presentations quickly, we don’t automatically become better at our jobs. If these steps don’t improve the bottleneck in our process – the key link where the real value is produced – then, as in the chicken coop example, they’re just as likely to create pile-ups and distraction, without actually boosting our true productivity." https://calnewport.com/on-bottlenecks-and-productivity/ #GenerativeAI #TheoryOfConstraints

Mastodon.green

@timolaine @jamesshore

I think: it always was.