Min-jun Park · 2026-02-18
Notebook habits that survive the first on-call weekend
runbooks · teams · azure
Administrators inherit messy histories. A notebook that only captures commands is useless if it hides why those commands were considered safe.
We coach a four-line minimum: trigger, hypothesis, action, verification. Even if the hypothesis was wrong, the record helps the next responder avoid repeating a dead end.
We also encourage linking to dashboards rather than pasting volatile numbers. Numbers rot; links refresh.
When the weekend ends, we spend fifteen minutes converting rough notes into a short postmortem draft—even if no incident occurred. That habit trains concise writing before stakes rise.