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.
Too many things doing too many things is an apt description for the age we live in.
Today, the average code that even a product manager or junior engineer submits is actually excellent overall - if your processes, harness and CI etc are well designed. It is actually super easy to author software well now. Whether you build something that is actually needed and is tasteful is another matter.
99% of the security vulnerabilities being found and exploited today were created by people. Cutting most of them out of the technical details is actually good.