The article equates effort with lines of code a bit too much for my taste. That said I think this model can be useful to describe how maintenance works in a given project.

Between this and the scrapers behavior... the disregard for infrastructure and best practices is obvious. It's just another externality those so called "labs" don't want to deal with. And well, it makes for a marketing stunt each time isn't it?

Unexpected metaphor but it kind of works. Indeed, architecture work is expensive, that doesn't make it unnecessary.

Or how Amazon manages to enshittify things even outside of its platform...

I'm not agreeing with some of the points in here. That said the core position of "it should be about collaboration not automation" I'm very much aligned with. It's after all at the center of how we designed AI systems in my team twenty years ago. We really wanted systems helping the user in their task and so co-constructing the result with the support of the machine rather than some kind of "oracle"