The Good Bad Bug: Fail Your Way to Better Code
summary
Claim: systematic, blameless failure tracking yields better systems. Evidence: the FAA incident reporting collects small events so investigators spot patterns; U.S. 2015 stats show 3.1 car deaths versus 0.05 plane deaths per billion miles (about 64× difference). Concrete software-era cases: hardware limits produce Space Invaders speed-up which testers prefer; a wrong AI makes police ram racers and births Grand Theft Auto; Playstation pop‑in leads to the Silent Hill fog workaround that becomes a feature.
AI-written summary · about
chapters (34)
- 0:00Intro
- 0:50Who am I
- 1:04Learning to Pilot
- 2:05Flat Tire
- 3:18Road Accidents
- 4:49Statistics
- 5:33What is failure
- 5:59The absence of success
- 6:24Definition of failure
- 7:16Space Invaders
- 8:09Modern History
- 8:59Testing
- 10:25Success
- 10:56Fail
- 11:42Video Game Development
- 11:59Street Racing Game
- 12:43The Concept
- 13:14Games
- 15:30Fog
- 15:45Fog in Silent Hill
- 16:24Aviation and Automobile Accidents
- 17:34We have a lot to learn
- 17:50What should that system look like
- 18:05You are not the problem
- 18:22They never stopped
- 18:51They verified
- 19:36Now we know
- 20:31Document everything
- 21:02How to document
- 23:02Documentation
- 23:49Learning from Failure
- 25:46Is it safe for me to fail
- 26:14My story
- 30:18My advice
related talks
39mThe Good Bad Bug: Fail Your Way to Better Code
34mThe Good Bad Bug: Learning to Embrace Mistakes
34mWhy Good Software Goes Bad
26mA Practical Taxonomy of Bugs
37mYour Software is Broken — Pay Attention
40mBuilding Resilience: How to Learn More from Incidents
01h 19mHow Code Fails in the Real World
33mBackwards Scoring: Ranking Test Suites by Which Real Incidents They Would Have Caught