I’m a software architect and engineer with a decade of experience designing secure, scalable systems for the cloud, but more than that, I’m someone who enjoys digging into the how and why behind the systems we build. Whether it’s debugging a tricky memory issue in Go, streamlining infrastructure with Terraform, or pushing for clean, testable architecture in a fast-moving team, I approach engineering as both a craft and a process of continuous discovery.

This blog is where I share what I’ve learned, from deep technical dives and architecture patterns, to thoughts on engineering culture, infrastructure hygiene, and the occasional odd edge case I couldn’t stop thinking about. My writing is driven by the same mindset I bring to my work: clarity, curiosity, and a bias for making things better, not just bigger.

Over the years, I’ve led pods/teams, mentored engineers, and helped define platform architecture while staying hands-on in the code. I believe technical leadership isn’t about managing people; it’s about shaping the path, reducing friction, and modeling high standards. Whether designing a system from scratch or helping a team scale their practices, I aim to be the kind of engineer who unblocks, enables, and builds with purpose.