I TURN COMPLEXITY INTO STRUCTURE
I build backend systems for problems that aren't always straightforward.
I like understanding how things fit together, figuring out what actually matters, and turning that understanding into software that works reliably in production.
↓ KEEP READINGWHEN EVERYTHING IS CONNECTED, NOTHING IS OBVIOUS
Requirements. Constraints. Legacy decisions. Distributed systems. Real-time data. Hardware. Protocols. Performance.
Everything affects everything else.
Understanding those relationships is often harder than writing the code itself.
The hardest engineering problems aren't solved by writing more code.
They're solved by understanding the system well enough to know what code should exist in the first place.
HOW I THINK ABOUT ENGINEERING
The Engineering Notebook is where I explore the decisions behind real systems.
The constraints, trade-offs, unexpected problems and reasoning that don't always fit into a project summary. Not just what I built, but why I built it that way.
Explore the Engineering Notebook →A LITTLE ABOUT ME
I like understanding how things work.
Not just the code, but the whole thing: what the system is trying to achieve, what constraints it has, where the pieces connect, and what happens when something inevitably goes wrong.
I've spent my career building software in different environments, from backend platforms and data-processing systems to software running on industrial hardware.
Some of those systems were well understood from the beginning. Others weren't.
I've always found the second kind more interesting.
The messy ones. The difficult ones.
The ones where you need to step back, make sense of what's there, and figure out where to go next.
More about me →LET'S TALK ENGINEERING
I'm interested in complex backend systems, data processing, performance, and the engineering decisions that make software reliable in production.
If you're working on something challenging, or simply want to exchange ideas about engineering, feel free to get in touch.
Get in touch →