If Hope Is Your Strategy, You’re Doing On-Call Wrong
summary
Sérgio Amorim (Revolut) explains how on-call should be an engineered practice rather than “hoping nothing breaks” when operating services for tens of millions of users. He describes using observability, proactive monitoring, and early incident detection as structural parts of the product, plus team practices for handling high-pressure incidents so outages are anticipated by design rather than discovered by users.
AI-written summary · about
chapters (7)
- 0:00On-call struggles
- 3:54The nightmare incident
- 5:00Autopsy of failure
- 5:21Prevention plan
- 27:02A few moments later
- 28:45The revelation
- 30:31Your move
related talks
30mOn call does not have to suck
31mHow to Build a Healthy On-call Culture
49mAgainst On-Call: A Polemic
44mYou build it, you run it
22mRaise a Production System:Making on-call human-scale w/ Observability & Trust
28mBuilding a healthy on-call culture
06mIgnite: Key Factors for Successful 24×7 On-Call Duty
05mOn-Call in a World Full of Toil