If we want to continue to ship at that speed we will have to. I’m not sure if we should, but seemingly we are. And it causes a lot of problems right now downstream.
Using AI to ship more and more code faster, instead of to make code more mature, will make this worse.
With coding agent projects I find that investing in DRY doesn't really help very much. Needing to apply the same fix in two places is a waste of time as a human. An agent will spot both places with grep and update them almost as fast as if there was just one.
It's another case where my existing programming instincts appear to not hold as well as I would expect them to.
Is the goal basically a codebase where your interactions are mediated through an LLM?
A bloated table codebase isn't good code, because it's harder to understand and makers changes to than the equivalent non-bloated codebase.
But... bloat does look a little bit different when you no longer need to optimize code for saving humans typing time.
Much of the confusing code I've encountered during my career has been confusing because it had too many layers of indirection, which happened because someone was applying DRY too aggressively because they didn't want to duplicate even the smallest pieces of logic in more then one place.
Good coding agents will only DRY like that if you tell them to.