The Good Bad Bug: Learning to Embrace Mistakes

on YouTube ↗34m

" summary

Sums failures to concrete takeaways: aviation’s mandatory error reports and aggregation reduce deaths so that cars kill 64x more people per same miles; games turned processor limits into mechanics — Space Invaders’ speed-up and Silent Hill’s fog — spawning genres and franchises (Grand Theft Auto); practical workflow changes matter: keep a paper or searchable log, write tests, extract patterns, run blameless postmortems, reward experimentation, and treat bugs as Good Bad Bug opportunities to learn and build something useful.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 4:57Sinking feeling in the pit of
3. 15:331. avoid placing blame
4. 16:36HOTEL

" related talks

• 39mThe Good Bad Bug: Fail Your Way to Better CodeJessica Rudder · RubyConf AU 2018
• 39mThe Good Bad Bug: Fail Your Way to Better CodeJessica Rudder · RubyConf 2017
• 34mWhy Good Software Goes BadRein Henrichs · Ruby on Ales 2016
• 29mLearning from incidents: how things went rightNick Stenning · LeadDev Berlin 2019
• 26mA Practical Taxonomy of BugsKiley Stradley · Keep Ruby Weird 2016
• 29mLooking under the rug: the art of learning from failureIsabella Silveira de Souza · JSConf Budapest 2019
• 30mPilot your Project: Avoiding Anti-Patterns While Handling Incidents and PlanningJessica Breckenridge · DevOpsDays Rockies 2016
• 49mBugs in Collaboration: "Learning from Incidents" EditionRuss Miles · YOW! Melbourne 2022