About Me

My journey, principles, and what drives me as a software engineer.

The Story So Far

I didn't start coding because I liked computers; I started because I wanted to solve problems. My journey began when I was trying to automate a tedious data entry task at a local business. Writing that first script felt like magic—the ability to turn logic into a tool that saved hours of human effort. Since then, I've been hooked on building systems.

Currently, I focus on full-stack development with an emphasis on scalable backends and highly interactive frontends. I believe that good engineering is about trade-offs, and there is no "perfect" tech stack—only the right tools for the specific business context.

When I'm not writing code or designing architectures, you can find me reading about system design, experimenting with new UI frameworks, or contributing to open-source projects.

Engineering Principles

User-Centric Design

The best systems are invisible to the user. Performance and reliability are features.

Keep It Simple

Complexity is a liability. I prefer simple, maintainable architectures over trendy tools.

Observable by Default

If a system breaks, we should know exactly why. Logs, metrics, and tracing are not optional.

Iterative Delivery

Deliver value early and often. Perfect is the enemy of shipped.

Want the full professional history?

Download my resume for a detailed view of my experience and education.