SRE

Practical SLO design: pick SLIs that matter, set realistic targets, define error budgets, alert on burn rate, and make the budget drive engineering tradeoffs.

Production incident response: clear roles (IC, comms, ops), runbooks that are actually useful, blameless postmortems, status pages, and how to learn from outages.

How to run on-call without burning out engineers. Rotation schedules, severity definitions, runbook templates, escalation, follow-the-sun, and the patterns from teams that ship reliable systems.

Chaos engineering done right. Game days, failure injection (Chaos Mesh, Gremlin), what to test, the observability needed, and the cultural shifts that make it stick.

What changed in observability since 2020. Wide events vs three-pillars, SLOs as the unit of conversation, OTel’s role, and how to actually find problems in production.

Practical incident response in 2026. Severity levels, IC role, comms cadence, runbooks, blameless postmortems, action item tracking, and the cultural shifts that produce real learning.

The resilience patterns every backend engineer should reach for: circuit breakers, bulkheads, backpressure, deadlines, jittered retries, and the production tradeoffs.

A short, practical guide to SLOs and error budgets for application developers. Choose the right SLI, pick targets you can actually defend, calculate the budget, and use it to drive feature-velocity vs. reliability tradeoffs.