How to Tame Bugs in Production: Successful Bug Managing Strategy in Five Steps
summary
Clear five-step recipe: accept bugs as normal, evaluate impact by actual user counts and business loss (Candy Crush Saga cites 255 million monthly active users and tradeoffs like skipping an Apple re‑review), use crash analytics and event tracking plus data scientists to find root cause, communicate via an incident Slack channel plus community posts or in‑game messages, and implement hotfixes or kill-switchable features as plan B — examples show hotfixing an ad CTA for revenue and using forum posts when a Google SDK crash is unfixable.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:50Firefighting analogy
- 2:36About Elena
- 5:05Map Balloon
- 7:36What can you do
- 8:10Things to take in mind
- 11:56Step 1 Evaluation
- 13:08Exercise
- 17:09Example
- 20:36Identify the problem
- 21:34Track events
- 22:34Communicate
- 24:44Candy Crush example
- 27:28Hero example
- 30:19Find a solution
- 33:42Learn
- 36:16Summary
- 37:12Questions
related talks
36mHow to defuse a bomb Wait, I mean a bug
04mWhat Bug Hunting Taught Me About Hunting Bugs
11mWorking with sharp tools - A case study of Continuous deployment
39mAdventures in Bug Hunting
28mTesting Isn't Enough: Fighting Bugs with Hacks
22mWhy Your Bug Rate Isn’t a Code Problem: Engineering for Unstable Work Intake
51m82 Bugs I Collected in a Year You Won’t Believe Made It to Production
50m#BugsZero