> There used to be a time, in the dark dark ages of history, 10 years ago or so, when I would encounter issues during the course of my work, and I could fairly

> There used to be a time, in the dark dark ages of history, 10 years ago or so, when I would encounter issues during the course of my work, and I could fairly confidently assume I was doing something wrong, or I just hadn’t read the manual correctly. Hehe, I remember those days :D Yes, code has gotten A LOT worse, and right now, whenever I pick a new library, I expect it to have bugs. A lot of people will start coding and bring in a TON of open-source libs, each with their dependencies. And then when something goes wrong, spend an insane amount of time just figuring out who's to blame. Or, just fix the symptom and continue. Clearly, the above won't work in the long run. But who cares about that, at the current pace of business, it'll be someone else's problem in a few months? They'll get promoted or switch jobs :D I'm on the opposite side of the spectrum: I choose VERY FEW libraries, go for mature ones, and do quite a bit of testing. For pretty much each library, I simply add an extra layer on top of it, so I don't need to deal directly with it, just in case I may want to later switch to another implementation, or perhaps do some workaround until the issue gets fixed. And this brings me to Microsoft: the code since Windows 8 (2012) has been beyond horrible, and their direction has been, lets say, "flexible" (to read: as the wind blows). I've discovered so many CRITICAL bugs, I've had to struggle with depression for months. > I want to rely on other code, but more and more I find that it’s safer to just assume it’ll be broken from the start. Yes, that is definitely a safe bet. The more you rely on 3rd party libs, the more you increase the risk of (critical) bugs. The more libs you use, the higher the risk. It's a really dim picture -- but something we unfortunately need to deal with. It's the new reality, and we just need to adapt :D