DevOpsDays NYC 2020: Quincy Iheme - Don't Fail Fast. Learn Faster

Channel:
Subscribers:
42,400
Published on ● Video Link: https://www.youtube.com/watch?v=Vh0EyBdBZdQ



Duration: 5:30
1 views
0


Gene Kranz is quoted as saying “Failure is not an option” during the Apollo 13 disaster. But let’s face reality, there was a huge failure: Apollo 13’s Service module was seriously damaged and if things stayed the same people were going to die. In his book “Failure: Why Science is So Successful” Stuart Firestein dispels the idealized myth of science and makes the case that Failure is a key element in the advancement of Science. I will present a 2 by 2 chart with Learning (low to high) and Blast Radius (low to high) as a way to think about how to design/think about experiments and projects.

Quadrant 1 (Low Learning, Low Blast Radius) is basically a waste of time, equivalent to rebooting Windows to fix a problem. Little damage, but also little learning and worse we destroyed all the evidence.
Quadrant 2: (Low Learning, High Blast Radius) this is Ugly. Will touch on the 1907 The Quebec Bridge Collapsed, in which 84 people died and little was learned from the warning signs along the way.
Quadrant 3: (High Learning, High Blast Radius) this is potentially redeemable. Will touch on United Flight 173 and while people died, a lot was learned from that flight and the black box data, that saved many future lives.
Quadrant 4: (High Learning, Low Blast Radius) this is Beautiful. Will discuss the Pixar method of iterating over a film and its story 100K+ times, staring with low cost rapid story sessions to go from “sucks to great”
Will then provide some practical heuristics for helping people limit blast radius and increase learning, such as running Pre-Mortems, Failure Weeks, Building Software Black Boxes (ala plane Black Boxes) and Mentioning some of the design patterns from “Release It!” by Michael T. Nygard.

Will touch on how to better react to failure personally and help others learn from failure.




Other Videos By Confreaks


2022-09-20DevOpsDays NYC 2020: James Meichle - Cooperative Economics for Engineers; or, Why You Have ...
2022-09-20DevOpsDays NYC 2020: Sponsors - Day 2
2022-09-20DevOpsDays NYC 2020: Kris Buytaert - 10 years of #devops, but what did we really learn?
2022-09-20DevOpsDays NYC 2020: Chen Harel - Reliability Scoring: A 3-Part Formula for Promoting Reliable Code
2022-09-20DevOpsDays NYC 2020: Jameson Hampton - Lessons in Ethical Development I Learned From Star Wars
2022-09-20DevOpsDays NYC 2020: Sposors - Day 1
2022-09-20DevOpsDays NYC 2020: Angel Rivera - CI/CD Agility and Controlling Pipeline Sprawl
2022-09-20DevOpsDays NYC 2020: John Allspaw - Can Resilience Engineering be sufficiently described in 5...?
2022-09-20DevOpsDays NYC 2020: Victoria Geronimo - DevSecOps is a Misnomer
2022-09-20DevOpsDays NYC 2020: Michael Wytock - Infrastructure Changes, So Modularize and Version Your...
2022-09-20DevOpsDays NYC 2020: Quincy Iheme - Don't Fail Fast. Learn Faster
2022-09-20DevOpsDays NYC 2020: Rachael Ferguson - Productionalizing Data Science Models
2022-09-20DevOpsDays NYC 2020: Christine Yen - Observability for Developers: How to Get From Here to There
2022-09-20DevOpsDays NYC 2020: Welcome and Intro
2022-09-20DevOpsDays NYC 2020: Janna B. Dogan - Are you ready for production?
2022-09-12DevOpsDays Boston
2022-09-06PowerShell+ 2019 - Wardley Maps Saved The Day - How Stack Overflow Enterprise... by Chris Hunt
2022-09-06PowerShell+ 2019 - Continuously deploying SQL code using Powershell by Kirill Kravtsov
2022-09-06PowerShell+ 2019 - It’s PowerShell In the Cloud – Welcome to Azure Cloud Shell by Michael Bender
2022-09-06PowerShell+ 2019 - Demystifying Microsoft's Cloud Automation products by Jaap Brasser
2022-09-06PowerShell+ 2019 - Introduction to Serverless Functions by Kirk Munro