About

Most of my career has been spent in the middle ground between a working prototype and a product people can depend on. I take projects from early architecture to the version that handles real load and real money, and I usually stay long enough to see the second rewrite.

The work I'm most useful for is judgment. After enough years in the field you recognise the same problems in different shapes: which decisions are reversible, which ones constrain you for years, when to invest in tooling, when to ship the imperfect version and refine in production. Good code matters, but the discipline to know when not to write it matters more.

My work today is in crypto and AI. In both, the interesting work sits where a wrong call is expensive to undo: the schema you cannot migrate cheaply, the failure that only appears under load, the operational work nobody budgets for until the first incident.

I'm a builder by instinct and a CTO by role, which means I still read code, still write the hard parts, and still believe the team's bar is set by what the person at the top is willing to do themselves.

Based in Poznań, Poland. I stay open to new things and make time for the right ones, including occasional advisory work alongside.