Commentary

Nate’s take on AI in production, reliability metrics, and how engineering teams work.

Use interruption patterns and responder feedback to change paging, coverage, and recovery expectations when on-call work becomes unsustainable.

September 29, 20233 min read

Give teams clear service ownership, decision authority, and capacity to act on reliability evidence before the next incident.

September 28, 20233 min read

Choose an SLI, target, and evaluation window that reflect user experience, then agree on the decisions an SLO result will change.

September 28, 20233 min read

Connect telemetry, customer reports, decisions, and verification so improvements in a dashboard reflect improvements in the service.

September 28, 20233 min read

An error budget translates an SLO into an allowed amount of bad service. Its value comes from the decisions attached to consumption and burn rate.

September 28, 20233 min read

Choose a small set of reliability indicators with clear definitions, useful distributions, and an explicit decision attached to each.

September 28, 20234 min read