Let me play devils advocate:
Even if individual code is of higher quality, if there are more pieces of code talking to each other, there are many, many more failure modes because software often fails at its interfaces. Nancy Leveson from MIT has written well on this subject.
Perhaps a bad example, but isolated code will often fail less than networked code that has to interact with a bunch of stuff. An old “dumb” tv never seems to have software issues, my new “smart” tv consistently has issues. It’s like having a dozen people write a paragraph each or a single person write a paper. Even if the single persons writing isn’t the better than everyone else’s, you’ll often get a more coherent paper.
I think you hit the nail on the head. In general software is far better than it's even been in the past. The problem is we use it more, and do more with it than ever. Where we had one main fast path in the past, suddenly the tree of what the software can do explodes in to dozens or hundreds of possible routes with different performance characteristics. Oh, and every one of those paths better be secure or it will all explode in a ball of fire.
Too many things doing too many things is an apt description for the age we live in.