01:26 - Resilience Engineering and Closed-loop Communication
06:55 - Acknowledging Burnout in the Developer Community
09:31 - Professionalization and Formal Training
17:41 - Reliability vs Resilience
20:40 - Resilience in the EMT Context
22:21 - Scene Size-up in Software
25:20 - Thai’s Superpower: The ability to remain calm in emergencies;Tech => EMT => Tech + Missing Seeing People You’re Helping
32:11 - Incident Response + Studying Incident Response; Normalization of Deviance
40:16 - Asking Questions
Jessica: Part of resilience is how do you know where to get help? When to ask for help and who to ask.
John: Following up with the cognitive interview idea.
Sam: Being explicit and deliberate about thinking about process and communication as a thing that you can get better at, that you can work on, and that you can talk about.
Thai: Cognitive interviewing Pokémon. Plus emotions as a state machine.
To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.
Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!Support Greater Than Code