FILIP MIKINA
Solving problems with(out) code, duct tape, and coffee empathy.
A little about me
Let's start with the obvious:
the best code I've ever written is no code at all. I work at the intersection
of SRE
and software engineering — I love writing code, but I'm always weighing whether it's worth the long-term
cost. Every line you write is one you have to maintain, debug, and eventually
replace. That's why I think carefully about adoption, rollout plans, and whether
a solution justifies its complexity.
At the same time, technology fascinates me. When I have the time, I love pushing
boundaries and going right up to the edge of overengineering in personal projects.
It's how I experiment, learn, and, honestly, what keeps me excited about building
things.
What I work on
Most days, you'll find me wrestling with distributed systems, making
monitoring tools that don't suck, and trying to convince CI/CD pipelines
to play nice. I've built systems that churn through 500k+ monitoring
samples per second, process thousands of messages per second, and somehow
managed to help teams ship faster without everything catching fire
(well... not always?).
Language-wise, I'm agnostic. I've shipped production code in Python, Scala,
Java, TypeScript, Go, Bash, Hack/PHP — you name it. Go happens to be my current
favorite, but tomorrow it might be something else. For me, the tool should
fit the problem, not the other way around.
Where I've been
My career has been a bit of a tour through different corners of tech. I've
worked at massive companies like Meta, Microsoft, Google, and Amazon,
where you learn how systems scale (and break) at ridiculous volumes. I've
also spent time at smaller, engineering-heavy places like Radix Trading,
where every line of code matters and there's no room to hide behind
process.
One of the most eye-opening experiences was my time at GetInData, a consulting
company where I primarily worked with startup clients. Consulting taught me
how to quickly dive into someone else's codebase, understand their business
problems, and deliver solutions under tight timelines.
If you're here
If you’re interested in hiring me, check out my resume . And if you enjoy thinking about distributed systems, automation, or how to make software teams happier and faster, subscribe to the blog ( RSS). I write when there's something worth saying, though.