I have to disagree here based on experience--the majority of software projects I've worked on really didn't care much for "quality" in any sense.
A HUGE portion of work in f500 companies that are non-software firms is outsourced--these companies spend loads of cash on consulting companies (yes, those ones) that often produce results to which the description of sub-par would be a compliment. There's been various cases made public, but more often is routine and poor quality mundane work that's way over budget and barely meets requirements.
If anything, the prevalence and adoption of LLM-generated code will increase the quality in a lot of places.
If you've never had to wade through something that one of Those Companies wrote, you have no idea how bad it gets and how frequently this is the case.
We just saw DOGE-related cuts to Accenture and Deloitte--these companies have huge contracts all over the place, not just public sector.
There's a massive amount of crap out there.
Most companies do not care, do not understand "quality" outside of some cargo-culted notion of "clean", have only adopted modern practices as some sort of ritual* of Things You Do without any assessment on what tangibly works or doesn't, have no understanding of how to attract skilled professionals, nor assess them, nor nurture them. Often their definition of skilled is a resume that contains the proper "experience" with whatever Java/Angular/React/we-love-containers thing they use. With the right number of "years" near it.
*a recent example--company has GH Actions with CI/CD for every commit on all branches but routinely suffers delays due to misconfigurations, runner issues, and other headaches. Code Reviews for PRs exist but are basically pedantry that just slow down deployments ("change this to switch over if-else") while missing crucial bugs, randomly updating major dependencies cause vague security warning that breaks interfaces and other APIs. All this and more--and this is one of the better examples I can think of, in terms of "quality."
I'm saying this as I worked at a Pretty Good consulting company that's business model changed to sub-outsourcing some of the labor to some of These Companies and often had to fix, assist, push back on, work extra to clean up, the various decisions made in these cases.
I also "inherited" and worked on fixes for things left behind by some of these places.
Good thing is there often was low-hanging fruit. Extra and overprovisioned cloud resources wasting $$ and the like, absurd architectures with extra dbs and queues, and all sorts of nightmares.