Greater Than Code
Greater Than Code
121: Emergency Communication with Thai Wood
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
The Field Guide to Understanding 'Human Error'
32:11 - Incident Response + Studying Incident Response; Normalization of Deviance
40:16 - Asking Questions
Cognitive Interviewing Techniques
The Checklist Manifesto: How to Get Things Right
Reflections:
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.
Check out with the “Working With Other Humans” track that Sam is running at RailsConf 2019 from April 29 - May 1 in Minneapolis, Minnesota.
Thai: Cognitive interviewing Pokémon. Plus emotions as a state machine.
John’s Hacking Your Emotional API Talk
This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode
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!
Special Guest: Thai Wood.
