This is one of those predictions that sound very wise and do well on Hacker News, but will turn out to be completely wrong. For the simple reason that we’re basing all our assumptions on decades of learned behavior predicated on coding being expensive. Writing code has historically been expensive and, by extension, so is maintaining it.

But when you can literally generate a whole codebase in a few hours, a lot of these assumptions don’t hold up. That doesn’t mean you don’t need sound logic and maintainability. But a lot of the small things you think would go wrong because of a bloated codebase stop being meaningful objections when you can keep generating, testing, and reworking it until those issues are resolved.

A lot of what we consider good engineering judgment is shaped by the constraints we’ve always worked under. I don’t think people appreciate how much of that changes when those constraints go away. The "slop" problem is ultimately a verification and testability problem.