For context, I've set up harnesses with recursive automated review loops, spec driven development, explicit lists, better models, better harnesses, formal methods tooling, etc. All of it helps, but they don't eliminate output issues. Those become very apparent when I go through the slow, manual work of deeply comprehending / validating LLM code.
And that leads me to one of three conclusions. Either my standards are achievable only by hyperintelligent programming gods, I have a skill issue using LLMs, or others aren't applying the same level of attention.
The first is obviously untrue. I meet my own standards and I'm an idiot. The second seems unlikely because I can see my competent coworkers and well-regarded people in the community discussing the same issues. So that leaves the third.
You could only argue about it when an engineer was in charge and even so when they're high up enough the pressures and incentives are to just ship fast and break stuff. Not every company can afford to be a NASA making uncrashable code that runs for 100 years and goes to pluto and all.
They don't know what n+1 problem is and they don't know about long-term maintainability.
overall software quality seems largely unchanged
OTOH, if someone insists on writing bad code—even after being advised otherwise—then they should expect to be out of a job.
Doesn't seem like "terminated junior developer" is the level of quality we should be accepting or promoting for AI.
In any case, the point is that low quality code shouldn't be promoted as the acceptable goal for AI.
How are people getting this "waste of time not to use AI" and "generates 99% of my code" level of code quality?
I know people's response will likely be something, something, "add instructions to memory to not use n+1", etc. But if the Ai wants to generate code this bad, then it represents an overall quality risk that would require an infinite memory file.