~/talk

What Romance Stories Taught me about Incident Management

Talkat DevOpsDays Philadelphia 2024 · 2024-05-14..05-15· [devops-and-delivery]
linkedin:ajuna
slides:none on file

Maps romcom beats to concrete incident practices and origins: describes the 1970 Laguna fire (12 days, 16 deaths, ~200 departments) that spawns the Incident Command System; argues for one Incident Commander, a single source of truth for comms, a designated note‑taker, automated metrics (time to respond/resolve), and regular postmortems. Mentions using Datadog for automation, cites Google SRE books as templates, and illustrates failure modes with a 27 Dresses case of cascading miscommunication.

AI-written summary · about

  1. 0:00Introduction
  2. 0:29Incident management meaning
  3. 2:55Romcoms and incident management
  4. 6:30Incident management in firefighting
  5. 11:3027 Dresses incident flaws
  6. 16:53Romance lessons for incident response
  7. 17:36Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.