#BugsZero
summary
Claim: bugs become rare after changing how work happens, not by writing more tests. Teams remove bug trackers and use a whiteboard, adopt mobbing and continuous pairing, stop introducing shared-state like global variables, and enforce immediate root-cause stops. Example numbers: one shop reports three production bugs in six years after mobbing; another documents 47 defects total by rigorously fixing each pattern. Tests act only as the outer control loop; tooling and refactoring to improve readability and eliminate context-dependent design prevent most defects.
AI-written summary · about
chapters (14)
- 0:00Whats a bug
- 5:00Sampling
- 6:30How many bugs
- 8:30Different camps
- 14:47Fault Tolerance
- 18:28Testing
- 20:53Causes of bugs
- 28:28Common causes of failures
- 29:48Complexity
- 31:08Most Common
- 34:18Other Common
- 37:08Context Dependent
- 44:18Refactor
- 47:43Errors of omission
related talks
39mClosing Keynote: Examples of How to Move towards Zero Defects
36mHow to defuse a bomb Wait, I mean a bug
42mBeyond “Just Try Harder”- Three effective strategies to tackle bugs
10mBeyond “try harder”: Effective strategies to tackle bugs
20mWill More Test Code Really Reduce Bugs…?
21mTHE MAGIC NUMBER
39mA Common Taxonomy Of Bugs And How To Squash Them
51m82 Bugs I Collected in a Year You Won’t Believe Made It to Production