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 through to the version that handles real load, real money, and real users, and I tend to stay long enough to see the second iteration as well.

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 focus today sits in crypto and AI. In both, I gravitate toward the parts of the system where engineering correctness compounds: the architectural decisions you cannot easily walk back, the failure modes that are expensive to diagnose, the operational layer that separates a working prototype from a production system the business can actually rely on.

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.