They’re quite pervasive.

🫲 Gestures broadly around at everything 🫴

Keeping all of my blood inside my neck.

Yes, but it is typically used for milk, like so:

The kind that requires this implement:

I think I’ll continue to enjoy my pseudonymity for the time being. Besides, I could link you to some rando’s modules, claim to be that person, and you’d have no way of verifying anyhow since this nick has no resemblance to the handle I used. But let’s just say, I shipped well-tested, thoroughly documented modules with very high “kwalitee” used by fortune 100 companies.

Processors change? Non-sequitur. Spectre an its ilk arrived on the scene at least a decade after MS had developed a reputation for shipping shit code.

Libraries become deprecated or vulnerable? Non-sequitur. Whose libraries? Who deprecated them? Remember, this is a company that personified Embrace, Extend, Extinguish. If they picked shitty vendors for libraries and did no due diligence on that source code, why are the externalities foisted upon users? Also, libraries don’t “become vulnerable” through some magical process. Either the bug was there from the beginning, or a shitty change was introduced and not caught.

Design paradigms shift? And this is an excuse for writing shitty code? I don’t buy it.

New integrations require new code and that means taking into consideration the new shape of the system. Sounds like they did a really shitty job of that and they make it the user’s problem.

Should we blame the old house builders for using asbestos? Unequivocally, yes. Those shitheads knew or should have known. Don’t believe me? Here is a handy link: https://www.sciencedirect.com/science/article/pii/S0169500224003623

Do note the decades between when it was understood the shit was dangerous and when the decline as a building material happened.

So, no, MS still does not get a pass.

False dichotomy. That was a business decision with externalities foisted upon users.

Go ahead, bro. It’s on CPAN.

Why did they write such shit software in the first place? No, they don’t get off the hook.

TL;DR;AS(AI Summary):

Title: Deep in Mordor where the shadows lie: Dystopian tales of that time when I sold out to Google

The blog post “Deep in Mordor where the shadows lie: Dystopian tales of that time when I sold out to Google” details the author’s disillusionment with Google after working there in 2007. Initially drawn to Google’s progressive image, they experienced overwork, underpayment, and a stifled culture that belied its promises – particularly regarding “20% time.” Attempts to voice employee dissatisfaction were met with management backlash, exposing a stark divide between full-time staff and exploited temps/contractors. This experience sparked a political awakening, revealing the inherent cruelty of capitalism and the moral compromises of working for a company built on surveillance and profit. The post critiques Google’s practices and, more broadly, systemic injustice, detailing a personal journey of realizing and resisting exploitation.