Well, it’s just my opinion, but sw development processes have changed quite a bit over the years…. About 20 or 25 years ago a number of “agile” methodologies became fashionable, and in the last 10 or 15 years “continuous integration/continuous deployment “ really took hold. Both of these were all about doing things faster, and the latter methodology in particular has placed much more of the onus on the developer regarding quality — I think most sw companies don’t really even have a QA team any more.
I work with a couple guys in my office that come from that background exclusively, and I’d say that they believe in software quality, but they place a much greater emphasis on the quality of the code as opposed to the quality experienced by the user. IE, they care how the sw does something more than they care about what it does.
I think web apps like Facebook, Google Maps, Amazon etc that are usually developed and deployed using agile methodologies, seem rock solid in terms of quality (I'm not saying what they do is nice or anything), especially given the massive scale at which they need to operate. They never even take the sites down for upgrades or anything, it all happens on the fly using load balancers.
The UI is different story, but even then they do A/B testing on that stuff, and what we get is supported by evidence that it works (for them, not necessarily for us the users).
I tend to associate low quality software with desktop applications. Agile methodologies might still be used for them, but it could be that the developers don't get as much (live) feedback from users there to do anything about defects. And then you have open source software (looking at you, Mozilla!), where you can go look at all the open issues on the code repository, and you can see bugs that have been known for years literally.
In all cases, developers are pressured to deliver on tight deadlines, so IMO that's where the blame should go.
