About me

Backstory

I've worked with DataLite since 2017 and grew there from junior through senior engineer to team lead. For the last several years I've been a self-employed contractor on their client projects. I'm at my best where correctness, compatibility and release safety matter, where the code meets domain rules, integration contracts and production.

I'd rather fix production than win an argument about it, and I expect the same from the people around me: real effort to get the work done and to keep learning.

Play style

Small, explicit changes

In a live system a precisely named rule, an isolated mapping or one focused test usually beats a big rewrite. Less to go wrong at 2 a.m.

Modern when it pays off

New versions and tools when they make the system more reliable, more observable or easier to change. Not for the CV.

Not done at deploy

The real system starts after deployment: old data, retries, external contracts, logs, metrics and whoever has to support it.

AI as a companion

Agents do as much as they reasonably can. The understanding, the review and the responsibility for what ships stay with me.

Nerfed Things I deliberately avoid

• Over-engineering. The "flexible" abstraction is usually the code everyone is afraid to touch two years later.
• Big-bang releases. A rollout needs an order, a fallback and a way to stop halfway, otherwise it's a bet.
• One-person architecture. I've been that person. It doesn't scale and it ruins holidays.
• Ego-driven choices. I once switched our side back to a partner's old format rather than defend a technically correct spec.

Offline

From the Krkonoše foothills, living just outside Prague with my family. I read a lot, mostly audiobooks (LitRPG and Czech sci-fi), play games to switch off, listen to metal and grind my coffee by hand.