The industry decided that simple infrastructure is for beginners and distributed complexity is for serious engineers. I disagree.

Call this "part 2" or just the “I-send-this-when-someone-says-Windows-is-fine-for-devs” edition. Old long post is here. Easy shots * Corpo bloat: macOS & Linux handle corporate bloat gracefully. Windows somehow manages to fight itself into lags * Builds: Same hardware. Same IDE. Same IntelliJ version. Same Java version. Same corporate junk (Defender,

A supposedly “Pro” Samsung 990 NVMe turned my home server into a biweekly reboot ritual. Meanwhile, a forgotten SK Hynix laptop SSD ran flawlessly for five years. Here’s how a boring Goodram and a FireCuda 530R restored my faith in hardware.

You know what? I miss when tech was quiet. Not "boring". Just quiet. You’d sit down, open your IDE, maybe browse a few blogs or forums, tinker with some open-source repo. It felt like a craft: like carving wood, or doing art, in a way. Now? It’

On May 28th, 2025, my ISP vanished from the internet - no DNS, no site, no support, nothing. What started as a casual “is your internet working?” turned into 20 hours of ISP outage.

Spoiler: it’s not your keyboard. It’s KDE’s appmenu module hijacking inputs and choking DaVinci Resolve under Wayland.

You ever stare at a map in a car-sharing app and think, "Umm, why does this whole area look… the same?" I spent 20 minutes driving around trying to figure out where the hell I was allowed to park.

We were deep into building a new microservice — one of those projects where the requirements were abstract, shifting, and open to interpretation. You know how it goes: "It's just a simple microservice, basically it should just save X and communicate Y back". Yeah, right... At first,

So, you finally made it to Senior Developer? Nice. 🎉 Now, let’s talk about what that actually means – because it’s not just about writing more code all day.