I mentioned that well-designed interfaces can help mitigate the chaos below, but interfaces can still hide serious issues, such as XSS, SQL injection, memory overflows, etc. It isn't "I want my code to be beautiful and pure," it's "I want my code to do what it says and not lead to issues for my client or users". It is disingenuous, patronizing and immature to suggest this could simply be a case of people not getting "emotionally triggered by ugly code".
A good engineer understands the difference; unfortunately our industry was already plagued with bad engineers, the majority of working developers are trash, and AI is just exposing this further by amplifying both good and bad practices. What I will not do however is acquiesce to these trash engineers and accept a new world where people are making giant abominations and sicking them onto the public without properly reviewing them first. 300 LoC would be a blessing compared to the 4 and 5-digit LoC PRs being thrown around in this new era. I don't care if trash engineers are 10xing their "productivity", when humans on the other end still have to deal with the slop. You can be a good programmer and a fast programmer and have multiplicative returns from agentic coding, all of these things can be true at the same time, and we should not excuse the lack of one trait in lieu of another.
> I would say that no, this is not sustainable, that at a fundamental level product quality is an emergent property of code quality, and the more your codebase drifts from the "platonic ideal" of what it could be if written and maintained by super good programmers, the more it accumulates flaws which WILL appear as bugs in your product.
The ability to anticipate these kinds of issues separates a good engineer from a bad one. The good engineers already recognize the unsustainability, and no amount of excuses from bad engineers changes that. And even more pertinent than eventual drift and loss of development velocity is the threat of security breaches, disruption of service or data loss. In the end, code is code, most people will never look at it. Aesthetics don't matter. Bad engineers often misinterpret good practices as merely "aesthetic" and think that engineers who care about their craft are simply emotionally attached to it. Don't fuel these people's misplaced fantasies.
I think at the end of the day, it boils down to whether the aesthetic quality of code / elegance is a big deal to you.
I suspect that you ask Codex to implement a feature and it uses a really dumb data structure, overly defensive programming, doesn't leverage helper functions, etc. and you end up with a 300-line abomination which could be 10 lines if you simply knew how to fucking program.
So what I'm getting to, is that some people like the parent probably don't care about producing 300-line abominations as long as it works. They don't care about neat abstractions or clever code. As long as the user testing shows a working feature and the tests are green. They don't get emotionally triggered by ugly code. So for them AI is amazing, they 10x their productivity (if not more)
Is this sustainable? I don't know. I think we're still in the early stage (Claude Code is only a year old). Intuitively, I would say that no, this is not sustainable, that at a fundamental level product quality is an emergent property of code quality, and the more your codebase drifts from the "platonic ideal" of what it could be if written and maintained by super good programmers, the more it accumulates flaws which WILL appear as bugs in your product.
I suppose the market will tell us soon enough.