Senior Backend / Full-stack Engineer
Distributed systems, API architecture, and database internals. I write software that handles real-world traffic and stays reliable at 3 AM.
Currently Exploring
→ Event-driven architectures at scale
→ The intersection of developer experience and system reliability
→ Writing as a tool for clearer engineering thinking
Principles
Code is read more often than it is written. I prioritize clarity and maintainability over clever one-liners. The best code is the code that does not need comments because it explains itself.
Distributed systems fail in unexpected ways. I design with failure in mind: circuit breakers, graceful degradation, and comprehensive observability.
Database constraints, transactional boundaries, and careful schema design prevent data corruption. Let the database do what it does best.
You cannot fix what you cannot see. Structured logging, metrics, and distributed tracing should be built in from the start—not bolted on when the first incident hits.
Connect
Interested in discussing backend architecture, system design, or potential collaborations? Let's talk.