been reading around a framing that puts the cost of AI-assisted code on maintenance, not dev throughput. whoever inherits the code carries most of it. that sits right for mature codebases. less obviou

been reading around a framing that puts the cost of AI-assisted code on maintenance, not dev throughput. whoever inherits the code carries most of it. that sits right for mature codebases. less obvious in greenfield, where the "next person" doesn't yet exist and the accounting is internal. I keep wanting a method that treats those as the same problem.