Everything I work on is an exercise in making unreliable things behave reliably. Patterns rarely do that; getting the trade-offs right does. For years that meant distributed systems — consistency, failure, scale, time. Now it means the same discipline applied to AI components that are non‑deterministic by design.
Currently a Staff Engineer at a fintech startup. I write about what I actually encounter, not the polished retrospective.
Recent writing
all posts →- No. 002
First, Make It Measurable
Notes on arriving at a startup where everything ran on 'more or less,' and on the order I proposed to fix it in — observability before velocity, velocity before architecture — and what each of those 'not yet's cost.
- No. 001
Killing a Monolith, Half a Tuesday at a Time
Notes on splitting a Spring Boot monolith into services without a cutover weekend, a freeze, or a rewrite — and on the four things that had to exist before the first extraction.