Weeks 4 and 5: three paragraphs, a full page Β· about 20 minutes
At two in the morning, the alert goes off. Errors are rising and users cannot load their pages. The first rule of an incident is simple: stop the bleeding before you look for the cause. If a release went out an hour ago, roll it back first and ask questions later.
Second, make roles clear. One person leads and makes decisions. One person handles communication. Everyone else works on the fix. Without a leader, five smart people can spend an hour talking past each other. The comms person posts short updates every thirty minutes, even if the update is "still working on it". Silence makes people worry more than bad news.
Third, after the fire is out, write a review without blame. Ask what made the mistake easy to make, and fix that. A good incident review makes the whole system safer, not just the one piece that broke.
How. Read one sentence. Look up. Say it in your own words. Then go on. Keys: β next, β back, Esc to show all.
Stop the bleeding before you look for the cause.
Every thirty minutes.
βοΈ -ize (US) and -ise (UK)
Pick one style and stay with it. US English uses -ize. UK English often uses -ise.
Watch out. analyze (US) / analyse (UK) uses -yze, not -ize.
Test yourself. The words hide. You hear a word, then type it.
π Linking words together
When a word ends in a consonant and the next starts with a vowel, join them: turn it off = tur-ni-toff.
How. Press π, then say it 3 times. Record yourself on your phone and compare.
Say each word out loud. Then make your own sentence with it.
incident
say: IN-sih-dunt
an event where something goes wrong
βWe had an incident last night.β
alert
say: uh-LERT
a warning message
βThe alert woke me up.β
roll back
say: ROHL bak
to go back to the earlier version
βRoll back the release first.β
communication
say: kuh-myoo-nih-KAY-shun
sharing information with others
βClear communication calms people.β
cause
say: KAWZ
the reason something happens
βWe found the cause of the bug.β