Success is often luck.
Failure is always data.
Not to mock the ruins, but to find the patterns hidden in the debris.
The Output
Where I Write
From regular shitposting to full-length survival guides. Choose your poison.
The Newsletter
Weekly deep dives into tech culture. One honest essay per week. The best way to stay in touch without the algorithm interference.
The Blog
Collected thoughts, coherent with a bit of luck. Longer than LinkedIn allows. No tutorials. Technical deep dives might happen, but only in a format that would give corporate PR a heart attack.
Regular doses of irony (3x a week). I try to be a "thought leader" without the lobotomy. Short posts served with a side of sarcasm.
IT Dictionary
The book. A translation guide for what people say vs. what they mean in IT. Essential for surviving meetings.
Fuckup Almanac
The series. Documenting the most expensive lessons in IT history. Because deleting production is the best way to learn (once).
The Philosophy
Why I write?
My Personal Motto:
"Some people need to take a shit in the morning,
others feel the need to perform an act of defecation."
I'm here for the first group. My goal is to cut through the noise, decode the complexity, and maybe—just maybe—help us build things that don't fall apart.
Because I can
Simple as that. I have a keyboard, an opinion, and just enough ego to publish it.
To kill the jargon
Yes, I use acronyms in meetings to survive. But here? We strip the "pompous BS" layers to see what things actually mean.
To show the patterns
The world is complex, but lazily repetitive. Systems—whether code, traffic, or corporations—fail in the exact same ways. It's time to map that.
Because systems are people
Talking about "systems" isn't just for nerds. It's about human behavior, bias, and crowds. Just with more electricity.
