- STATUS
- RUNNING
- UPTIME
- --y --m --d --:--:--
sparkline shape derived from current value + trend; per-day history lands with /content/skills/*-history.md
- compensation (indexed)
- equity (indexed)
- learning (indexed)
- health (indexed)
- family (indexed)
cost optimization wins
no entries yet — populate optimizationWins in /content/cost-economics.md
The book that taught me to chase explanation rather than formalism. Re-read selectively for the pleasure of it.
Short essays on the scale of things. Useful when the daily operational frame collapses too far inward.
The book that taught me to think of management as a system with leverage points, not a sequence of conversations.
Foundational early-career book. Still reach for it when I find myself overcomplicating something.
CURRENT INCIDENT (none)
CURRENT FOCUS — Q2 2026
Reliability program
- Rebuilding the surface area on the AI-assisted incident response work — the diagnoses are accurate; the UX needs to catch up before engagement follows
- Expanding chaos automation across the platform
- Continuing the long arc of structural reduction in highest-tier surface area — bringing the bar down by retiring or re-tiering work, not just by adding monitors
Platform and infrastructure
- AI Core Platform maturation — model serving, training, vector search, retrieval continuing to land under unified ownership
- Multi-year infrastructure efficiency execution
Org
- Promotion calibration cycle for senior engineering levels
- Continuing the staff-level career growth program in its biannual rhythm
Personal
- Running consistency — building back to a regular cadence
- Reading: TODO (current book)
- Family in the PNW; weekend hikes when the weather cooperates
warming up…
no entries yet — populate talksGiven in /content/talks.md
no entries yet — populate talksScheduled in /content/talks.md
no entries yet — populate writing in /content/talks.md
- Building reliability programs that scale faster than headcount
How to architect reliability as a system of systems with feedback loops — Prevention, Safe Deploy, Detection, Response, Validation — and why automated enforcement beats voluntary frameworks for cross-cutting concerns.
- Backwards-compatible API evolution at hyperscale
Lessons from introducing statefulness into a stateless API contract on AWS Lambda — async state machines, cache TTL as a consistency primitive, and how to ship a contract change for an ecosystem without breaking it.
- AI infrastructure is infrastructure
Why model serving, training, retrieval, and feature stores belong under the same engineering discipline that runs the rest of the platform — and what changes operationally when you consolidate.
- Cloud vendor strategy at nine figures
Designing the relationship, not just the contract — finding tradeable surface area, modeling commitment structures honestly, and why the best negotiation muscle is operational fluency.