Says it's unthinkably bad then proceeds to give only one example. There are several other issues you can list.
>the terminal -- the terminal! -- freezes after staying open several days, and you need to kill it and restart it.
I wonder when that issue ever happened since I'm always ssh'd into my homelab via the terminal for days and never had to restart it since it never froze.
>The worst part, I think, is how the brokenness ends up permeating the engineering culture. Malfunction is just normalized.
Microsoft didn't make the culture like that, the managers were always like that which made them choose Microsoft because they just choose the biggest corporate name brand supplier. It's your typical old-school MBA.
I've worked at all-MS shops and at all-Linux shops, and despite the issues with MS tech, the all-MS shops were far less toxic and pleasant to work at as people treated it as a 9-5 job instead of their own personal start-up project that needs to strictly conform to their world view, therefore the linux-shops I worked at tended to attract more of the toxic problem employees like your grandparent whos work life revolved around tech evangelism than pragmatism, which I didn't like since I just wanted to get work done and go home, not participate in some crusade at work to judge and shame choices of OS/IDE/languages/frameworks/tools the company should be using. As long as I get paid, I'll use any widely available tool, I don't really care.