Keeping systems boring.
I’m a Site Reliability Engineer who likes clean automation, useful observability, and calm incident response. When I’m off-call, I’m usually playing PC games or tinkering in the homelab.
Status: Operational
Services: --/-- up
Primary region: us-east
Today’s reliability snapshot
SLO-ish, but personal
Availability target
99.95%
Error budget
Healthy
On-call principle
Automate the pain
Preferred telemetry
Metrics + Traces
What I work on
Reliability themes, not buzzwords.
Observability
Signals that are actionable: SLOs, dashboards that answer questions, and alerting that respects humans.
Automation
Small tools that remove toil: scripts, pipelines, and guardrails that make the “right way” the easy way.
Incident Response
Tooling and processes to respond to incidents with speed and confidence.
Quick links
Places I’m active.