Zero-bug policy success
summary
A small remote startup fixes roughly 250 bugs through 2024, reaches zero-bug day after two intense months, then sustains near-zero backlog with 50% focus on fixes while shipping features. Critical errors drop to three incidents; most reports get fixed within days. Workflow relies on a company Slack fix-it-now-or-delete-it habit, a visible Notion bugs column, weekly rotations for first responders, and increased test coverage and end‑to‑end releases.
AI-written summary · about
chapters (19)
- 0:00Zero-bug policy intro
- 1:10What zero bug policy means
- 3:39Remote startup team context
- 6:04Origins of zero bug policy
- 8:13Team motivation to adopt
- 12:48Overcoming process hurdles
- 15:19Implementing in practice
- 18:52Fixing bugs and team bonding experience
- 22:04Balancing fixes and features
- 23:31Achieving zero bug day
- 25:36Long-term policy impact
- 30:34Bug management tools
- 33:59Common policy questions
- 40:59Testing effort considerations
- 42:48Stakeholder prioritization
- 45:22Was fixing all bugs worth it?
- 46:03Nuclear option for backlogs
- 47:31Lessons learned and tips
- 50:25Summary
related talks
54mZero-bug policy success
17mZero Bug Policy
36mHow to defuse a bomb Wait, I mean a bug
22mWhy Your Bug Rate Isn’t a Code Problem: Engineering for Unstable Work Intake
35mAvoiding the Petard: Triage at Scale in Firefox Quantum
11mOverhead, not downtrodden
48mWe're Good At Writing Software [Keynote]
11mWorking with sharp tools - A case study of Continuous deployment