Calm, practical engineering
I build software for the real world: reliable, maintainable, and easier to reason about over time.
The Story
I started working in software in 2011 because I wanted to help people use technology to build their business. Not just things that ran, but systems that were reliable, maintainable, and genuinely useful to the people depending on them.
That path took me through scrappy side projects, a real-estate startup, and eventually enterprise software at SPS Commerce, where I've spent years shipping products at scale. The throughline has stayed the same: build systems that hold up in real life and make the next decision clearer, not harder.
The Zen in Zengineer
"Zen" isn't about moving slowly; it's about staying calm under pressure while moving with purpose. When systems break at 2 AM or scope shifts mid-sprint, panic doesn't ship fixes. Clarity does.
In practice, that means debugging production incidents without losing the plot, then turning around and explaining tradeoffs clearly to stakeholders who need confidence, not noise.
That approach carries through the rest of the work too: clearer communication, steadier execution, and software that holds up in real-world conditions.
How I work
I prefer boring, reliable infrastructure over flashy over-engineering.
I write code I would be happy to read again in two years.
I treat documentation as part of the deliverable, not cleanup work for later.
I like systems that are observable, maintainable, and calm under load.
Need a calmer hand on the system?
If you need help with a new product, a migration, or a system that has gotten hard to reason about, I'd be glad to hear what you're working on.
Get in Touch