~/about
About
Engineering judgement, production mindset, and where the work is heading.
How I build
I work in small, reversible steps. I prefer boring code that survives review six months later over clever code that needs a thread to explain. The systems I'm proudest of are the ones whose on-call rotation got quieter after I left.
Backend & operations
Backend engineering, for me, is inseparable from operations. Observability, predictable delivery, structured logging, runbooks, idempotent retries — these are the work, not someone else's problem. I default to platform-shaped thinking even on small services.
Production mindset
Production is the user. Whatever ships either operates, recovers and informs its operators clearly — or it shouldn't ship. I'm comfortable in regulated and compliance-aware environments where this attitude is the baseline, not the differentiator.
Current direction: Platform / AI Platform / MLOps
The next step is Platform, AI-Platform and MLOps work, grown out of the same backend and DevOps foundations rather than replacing them. The operational patterns carry over: golden paths, reproducible environments, observable deployment, cost-aware infrastructure. Model and data workloads add their own constraints — lifecycle, evaluation, drift, reproducibility — but reward the same production rigor.
What I value
Simple systems over accidental complexity. Documentation written for the next operator, not the next reviewer. Code that admits what it doesn't know. Honest scopes. Calm engineering.