About
I've spent the past several years building backend systems that don't wake people up at 3 AM. My focus is on distributed systems, API design, and making complex architectures maintainable.
Most of my work has been on SaaS platforms where reliability and scalability aren't optional. I've built payment processing systems, real-time data pipelines, and multi-tenant architectures that serve thousands of users.
I believe good backend engineering is invisible. When infrastructure works well, nobody notices. When it fails, everyone does. That philosophy shapes how I approach system design: prioritizing observability, graceful degradation, and operational simplicity.
Technical Philosophy
- 01.Start with the problem. Technology choices should follow from requirements, not the other way around.
- 02.Optimize for change. Systems that can evolve are more valuable than systems that are perfect today.
- 03.Boring is beautiful. Proven technologies with well-understood failure modes beat cutting-edge solutions in production.
- 04.Measure everything. You can't improve what you can't observe. Comprehensive metrics and tracing are non-negotiable.
Beyond Code
When I'm not building systems, I'm probably reading about how other people build systems. I enjoy diving into engineering blogs, post-mortems, and papers about distributed systems.