While I have no particular love for AI generated code, I think this has nothing to do with AI. Software has been unreliable for over a decade. Companies have been rushing out half baked products and performing continual patches for many years. And it's our fault because we have just come to accept it.

> Software has been unreliable for over a decade

The "over" deserves a lot of emphasis. To this day, I save my code at least once per line that I type because of the daily (sometimes hourly) full machine crashes I experienced in the 80s and 90s.

Same, I think I should just turn on autosave at this point to save my fingers

I have this fear autosave might corrupt the file by trying to save while the program has hung or whatever.

I don't remember which app made me think that. Maybe some old version of Matlab cleared unsaved files when hung and with autosave enabled.

My prediction is that this will actually get better, because the cost to find and fix with AI is so much lower in time investment.

The problem is human, not technical. Companies and managers need to start caring about the details instead of crossing items off a list. Until we see that culture shift in the industry, which might never happen, AI isn't going to help—if anything, it'll make the problem worse as devs rush to deliver on arbitrary deadlines.

Well the reason I think it might be different is that I am noticing a material change in my behavior.

I have always cared a lot about quality and craftsmanship. Now when I am working and notice something wrong, I just fix it. I can code it entirely with AI in the time it would've take me to put it on an eternal backlog somewhere.

Plus, if you are skipping tests or telling yourself, you wrote them when they don’t actually verify anything in the first place, then buying into a hype cycle of “the AI writes perfect code“ is unlikely to break the pattern

AI doesn't ever fix anything, it just breaks stuff and adds technical debt.