Hi, I'm Robert.
Somewhere around year fifteen of building, breaking, and occasionally setting fire to software systems, I started writing about it. Not because the world needed another tech blog — the world has plenty of those, most of them written by people who've never debugged anything at 3am in production while a Slack channel melts down like a nuclear reactor with emoji reactions.
I started writing because I kept having the same conversations. With junior devs who thought testing was a punishment. With architects who drew boxes on whiteboards and called it a plan. With managers who believed you could purchase innovation like office furniture — just find the right vendor, sign the PO, and creativity comes out the other end. That's how art works, right?
What happens here
Technical guides — the kind I wish existed when I was figuring things out the hard way. Software testing from first principles to enterprise frameworks. Microservices architecture where the diagrams come with honest warnings. Docker and Kubernetes for people who just wanted to deploy a web app and somehow ended up managing a distributed system with feelings.
Satirical parables — darkly funny stories about the absurdities of tech culture. The hiring processes designed by people who've never done the job. The reorgs that solve organizational problems the way rearranging deck chairs solves icebergs. The colleagues who take credit like they take sugar — quietly, constantly, and without asking. If you've ever sat in a meeting where someone described their "AI strategy" using only buzzwords and confidence, you'll feel uncomfortably at home.
Industry takes — honest perspectives on careers, hiring, talent markets, and the things nobody tells you in bootcamps. No LinkedIn motivational energy. No "top 10 ways to 10x your productivity." Just the observations of someone who's been in the trenches long enough to know which trenches are worth digging.
Why "Codyssey"?
Code + Odyssey. Because every software project is a journey — sometimes epic, sometimes absurd, always longer than the estimate. The compass rose in the logo isn't decorative: it's a reminder that the best engineering is about knowing which direction you're heading, not just how fast you're moving. Although, to be fair, most of us are moving very fast in a direction we chose during a sprint planning meeting that ran forty minutes over.
The human behind the keyboard
I'm a QA architect based in Bucharest, Romania. Fifteen years in software engineering across testing, automation, architecture, and the occasional existential crisis about whether my career choices have been optimal. (They haven't. But the stories are better this way.)
Find me on LinkedIn, subscribe to the newsletter, or — if you have something to say — get in touch. I read every message. Even the ones that start with "Actually, I think you're wrong about..."