Backend · Systems · AI
I build backend systems, take ownership of problems end-to-end, and learn whatever the problem requires.
I write about SYSTEMS, ENGINEERING & AI - mostly questions I can't stop thinking about.
About
I wouldn't describe myself as someone who is passionate about simply writing code. I'm interested in understanding problems deeply enough to build the right thing.
As a software developer, I'm less interested in treating tools as black boxes and more interested in understanding what makes them work - the systems beneath them, the abstractions they rely on, the trade-offs they introduce, and the engineering decisions that shape them.
For me, understanding why something works is often more valuable than simply knowing how to use it.
That mindset becomes especially useful when the problem isn't well defined.
How I work
Give me the problem, not just the ticket.
I prefer understanding the problem, figuring out the constraints, choosing the simplest approach that works, shipping it, and staying close enough to the system to learn from what happens in production.
The interesting problems begin where there is no obvious answer.
Designing the architecture. Identifying failure modes. Finding bottlenecks. Challenging assumptions. Asking:
“What happens when this platform reaches a million users?”
Then finding out.
AI has changed how quickly software can be produced. That makes understanding the underlying system even more important to me.
I use AI to accelerate implementation, exploration, and iteration - but I don't outsource understanding. Generated code still needs to be reasoned about, tested, simplified, and owned.
I like starting with something I don't fully understand, building it from the ground up, breaking it, discovering why it broke, and coming back with a better understanding than I had before.
Every failure becomes another piece of the system I now understand.
My approach
Learn. Build. Break. Understand. Build better.
Whether you're dealing with a scaling problem, designing a new system, or simply trying to figure out why something keeps breaking, feel free to reach out.