About
Systems-minded developer who ships calm products.
I build distributed systems and interfaces that stay clear under load. Good work to me is reliable APIs, honest UX, and a release cadence you can trust.
Balance the moving parts and the whole stays readable.
Architecture with room to breathe
I start with contracts, reliability targets, and observability before polish. Small services, clear edges, and defaults documented in plain language.
- Edge/serverless where it helps latency
- CI that fails fast and explains itself
- APIs shaped to match the product story
Interfaces that stay calm
I cut UI copy to the bone, surface only the next action, and let motion serve feedback—not decoration. Accessibility and keyboard paths are non-negotiable.
- Microcopy that explains constraints
- State you can skim in a glance
- Loading/error states designed first
Sharp color blocks remind me to keep choices deliberate.
Ship, refine, sand down the edges—repeat.
Work cadence
I ship in weekly slices: a small feature, a measurable improvement, and one cleanup. You get demos, decision logs, and no mystery tickets.
If that sounds like the pace you want, let's build together.
Collaboration
I keep teams unblocked with short async updates, loom walkthroughs, and PRs that narrate the why, not just the what.
- Design partners looped in early
- Docs that age with the code
- Release notes that humans read
Momentum without chaos—like steady brushwork.
Reserving contrast for what matters most.
When things break
Incidents get briefs, not blame. We replay timelines, instrument the gaps, and ship guardrails so it doesn’t repeat.
- Alerts tuned to real impact
- Runbooks in the repo, not wikis
- Postmortems with one concrete fix