I’m most energized by work that sits at the intersection of product and engineering: building things people actually use, with systems teams can maintain and trust.
What I actively optimize for:
- Craft: readable code, good structure, and healthy defaults
- Usability: clear UX, strong affordances, and fewer sharp edges
- Ownership: reliability, operability, and low support burden
- Long-term thinking: making future changes cheaper, not harder
I value teams that make tradeoffs explicit, care about clarity, and treat engineering as a discipline of judgment—not just output.
I work best in environments where engineers are trusted to think, where feedback loops are short, and where quality and delivery are treated as complementary rather than opposing forces.
When those conditions are present, good software—and healthy teams—tend to follow.