Why we must approach debugging differently
summary
Claims a surprising metric: 75% of developers' time on bugs, backed by Coralogics. Demonstrates that classic step‑over debugging for first‑year exercises fails for cloud native systems because you can't recreate production locally. Recommends giving teams a cloud‑native toolbox (live debugging for serverless, integrated observability), changing backlog prioritization, enforcing team ownership and safe spaces, and collecting targeted data so fixes finish faster and actually reduce outage toil.
AI-written summary · about
chapters (10)
- 0:00Rethinking debugging approaches
- 1:40Debugging dominates time
- 2:42Bias against fixing
- 4:05Debugging culture stress
- 5:09Traditional debugging limits
- 6:34People and mindset in debugging
- 7:58Team ownership and safety
- 8:20Processes to reduce stress
- 9:22Cloud-native debugging tools
- 10:04Balancing data collection
related talks
15mDebugging debugging; why we must approach debugging differently
31mLow-Level Computing in a Cloud Native World
26mow to Enjoy Debugging in Production with Karen Tracey
26mThe Mindset of Debugging
42mBeyond “Just Try Harder”- Three effective strategies to tackle bugs
29mObservability for Developers: How to Get From Here to There
41mDetective Hat: Investigating Production Issues
40mThe Future of Developer Careers: When Dev and Ops Meet