About Me

I'm a backend engineer and team lead with 10+ years of experience, mostly in the .NET ecosystem working on backend and distributed systems.

My background includes building and evolving microservices, working with cloud platforms, and maintaining large existing codebases. A lot of my day-to-day work revolves around system design, migrations, performance considerations, and making changes to complex systems in a controlled and predictable way.

I'm currently a Team Lead, managing a team of 13 backend engineers. That means my responsibilities go beyond coding and include technical direction, architecture reviews, delivery planning, and helping teams make sound engineering decisions over time.

What I Write About

This blog does not contain private project code, internal business details, or proprietary design decisions. Instead, I focus on:

• My own projects and pet projects
• Open-source examples
• Generalized architectural patterns and trade-offs
• Analysis of public engineering blogs, talks, and case studies
• Practical observations from building and maintaining backend systems

The goal of this blog is to document how experienced engineers reason about problems—not to expose real systems, but to share thinking, patterns, and lessons that are broadly applicable.