Put any distro in front of me and provided I don't need to master it, I'm good. Ubuntu is fine. Debian is fine. RedHat is fine. Fedora is fine. I even have a tiny low-end system that is using Bohdi. Whatever. We're all using mostly the same kernel anyway.

90% of what I do is in a container anyway so it almost doesn't matter; half the time that means Alpine, but not really. That includes both consuming products from upstream as well as software development. I also practically live in the terminal, so I couldn't care less what GUI subsystem is in play, even while I'm using it.

The only time I've encountered people that care a little too much about what distro is being used, is right after having transitioned to Linux; the sheer liberating potential of the thing can make you lose your head.

I've come across a lot of professional bias about Linux distros, but that's usually due to real-world experience with tough or bad projects. Some times, decisions are made that make a given distro the villain or even the hero of the story. In the end, you'll hear a lot of praise and hate, but context absolutely matters.

There's also the very natural tendency to seek external validation for your actions/decisions. But some people just can't self-actualize in a way that's healthy. Sprinkle a little personal insecurity into the mix and presto: "someone is getting on great with that other Linux I don't use, so Imma get big mad."

Good point.

Calling in sick:

Calling in, sick:

Thank you!

I firmly believe this is how we wound up with tabs as a feature in the first place.

Thank you! I want to ::sniff:: thank my coach, the whole team ::sniff::, and especially my mom for helping make this happen! ::sniff:: Love you mom!

Here's a version for my fellow gluten-free peeps:

I just want to echo your sentiment with something I've been saying here for a while now:

Do not confuse information technology use for computer literacy.

Wait, is this a meme template for the Complaint tablet to Ea-nāṣir? That's incredible.

Honestly, this is why I tell developers that work with/for me to build in logging, day one. Not only will you always have clarity in every environment, but you won't run into cases where adding logging later makes races/deadlocks "go away mysteriously." A lot of the time, attaching a debugger to stuff in production isn't going to fly, so "printf debugging" like this is truly your best bet.

To do this right, look into logging modules/libraries that support filtering, lazy evaluation, contexts, and JSON output for perfect SEIM compatibility (enterprise stuff like Splunk or ELK).

Heisenbugs are the worst. My condolences for being tasked with diagnosing one.

At that point, you may as well just buy a school bus.