Background

I spent years working in product — close enough to engineering to realize I understood it better than I admitted. That tension between understanding a system and being able to build it became unbearable. So I learned to build.

Most developers write code before knowing what the code is supposed to do. I come from the opposite side. I know what something needs to do, why it needs to do it, and who it's for before a single line gets written.

That cross-disciplinary fluency — product thinking combined with engineering execution — is what I bring to every project.

Approach

Architecture first

Structure before syntax. A well-architected system is easier to debug, scale, and hand off than clever code with no coherent shape.

Product awareness

Every technical decision has a product implication. I hold both in mind simultaneously — what's correct engineering and what ships the right thing.

Clarity over cleverness

Code is read far more than it's written. I write for the next person in the codebase, not to demonstrate capability.

End-to-end ownership

I work across the full stack — database schema to UI interaction — because the best solutions don't respect layer boundaries.

Have something to build?

Get in touch →