Speaker Panel - Day 1
summary
Talk gives concrete moves: stop asking irrelevant algorithm questions, recruit from code schools, pay people to produce accessible primers instead of dumping PDFs, run 10-minute debriefs after incidents, run game days to practice, capture chat logs and do process tracing with draw.io diagrams or whiteboards, publish findings in a shared COE (coe.amazon.com) or weekly ops review, sponsor and train newcomers, and measure uptake by who shows up and who says they learned something.
AI-written summary · about
chapters (8)
- 0:00Resilience engineering panel intro
- 0:23Making engineering welcoming
- 12:12Learning from incidents
- 22:07Resilience as guerrilla movement
- 36:50Imposter syndrome in tech
- 43:02Personal resilience and hobbies
- 48:42Spreading postmortem knowledge
- 53:01Closing remarks and Q&A
