Arthur

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.

In tech, it’s easy to confuse complexity with progress. Adding layers, abstractions, or extra features can feel like you’re being productive—sometimes even impressive—like you're building something substantial. We’ve all seen codebases and systems that seem to wear their complexity as a badge of

Debugging. Well, it's not exactly the most shiny side of programming, is it? No boot camp is advertising with "Learn programming from us, so you could debug an app in just a week!". Usually there’s no standing ovation when you fix a bug that’s

Sick of paying for services you barely control? Self-hosting could be the answer, but is it? Can it be sold in your CV? Can you learn anything from it? Are there any other benefits? The short answer is yes and here's why.