Building scalable SaaS products,
AI-powered applications,
and modern web experiences.

A PC arrived home in 2004 and I've barely looked away since. Not for the games — though Counter-Strike stuck around — but for the realization that typed instructions make a machine do exactly what you ask. I taught myself to code through a mechanical engineering degree, and that original feeling of giving a system precise commands and watching it respond is still what gets me into the chair every morning.

Real-time systems, complex infrastructure, anything where state has to stay correct under concurrent load — that's where my attention naturally goes. Not because it looks impressive, but because the problems are genuinely hard and the margins for error are real. I like building things with operational weight: systems that have to keep working even when conditions get messy.

Most bugs I've traced in production turned out to be architecture decisions wearing the disguise of a code problem. Good structure gives a project the ability to scale, to be read by someone who wasn't there on day one, and to survive changes in requirements without collapsing. I treat architecture as the part of the work that outlasts any individual feature.

Technically correct software that nobody needed is still a failure. I want to understand the problem well enough to push back — to know when a simpler solution fits better, or when the real issue sits upstream of anything code can touch. That clarity is what makes the engineering decisions actually matter, and it's the part of the work I find most interesting.