Does it matter to the people requesting the software if it acts in the way they expect?
In fact, that's the entire reason we care about "quality code", because we assume that quality code is code that does what you expect well and consistently.
I say this as someone who hand writes code pretty much every night for fun, just to experiment with computation. Which, oddly, is more fun than ever because I don't feel like there's any need to connect this type of programming with "real world software", and I can really enjoy code for it's own sake, meanwhile my job is mostly just running agent loops (which I quite like as well).
That is the entire purpose of "quality of code".
If the end user experiences a correctly performing application, now, and in the future, they don't care at all what the code looks like.
AIs could resort to a single global array of primitives and forget all about functions, and just use gotos if it helped them (it probably doesn't).
At least for human-written code, there's usually a thought and concept to be discovered underneath. For LLMs, one-shotting is all they know, and getting them to consider months or years of expanding and changing requirements will quickly turn into an impossible game of Twister.