Our reading notes

On Call Rotations: How Best to Wake Devs Up in the Middle of the Night

A discussion of on-call as shared ownership, including the managerial work required to make it sustainable.

The idea to take with you

The rotation needs an owner who sees the human cost and turns repeated pages into engineering work.

What to look for

  1. 01

    Share system knowledge instead of depending on one expert.

  2. 02

    Review interruptions with the rotation owner.

  3. 03

    Make the consequences of operational load visible in planning.

Keep in mind

A reported talk with strongly opinionated language. Ownership does not justify unsafe fatigue or unbounded availability expectations.

Put it to work

Try this next

Review a rotation’s recent pages. Identify repeat alerts, missing runbooks, and recovery gaps; reserve capacity for the most costly pattern.

Get the reliability template

Notes and exercises by Awesome CTO. The original work belongs to The New Stack, reporting Charity Majors.

Work through the bigger question.

Our reliability guide connects the reading to a practical approach and a template.

Open guide
Esc

Type to search every entry. ↑↓ to move, Enter to open.