I'm a software engineer focused on architecture, complex systems, and long-term maintainability. I've owned complete implementations on multi-person teams and served as the sole developer on large production projects. My work tends to live where product complexity and technical rigor meet.

How I Work

Predictable over clever

I optimize for correctness and stability first. Explicit state, clear data flow, minimal magic. Code should be easy to understand and maintain six months later.

Thinking in constraints

I start by identifying failure modes and second-order effects. Understanding what can go wrong leads to more durable solutions than assuming everything will work.

Clarity over persuasion

My teaching background shows up in how I write, explain, and document systems. I care more about being understood than sounding impressive.

Tradeoffs, not best practices

Every decision has costs. I prefer discussing real tradeoffs rather than defaulting to dogma. Context matters more than convention.