Debugging debugging; why we must approach debugging differently
summary
Claims debugging is broken and consumes 75% of developer time according to a cited study; teams respond by swapping legacy methods for a cloud-native toolbox and dynamic observability that captures production data with no downtime. Practical changes include onboarding workshops for tools like Rookout, strict logging rules (meaningful messages, correct levels, avoid noise), preplanned bug prioritization, adjusted sprint commitments, and team-owned tickets; these concrete steps remove friction and speed root-cause discovery.
AI-written summary · about
chapters (6)
- 0:00Start
- 0:48Developers do a lot
- 1:43What would you rather work on?
- 7:12Resolving bugs early is cheaper
- 7:40Monitoring
- 9:15Dynamic Observability tools
related talks
11mWhy we must approach debugging differently
26mThe Mindset of Debugging
26mow to Enjoy Debugging in Production with Karen Tracey
25mDebugging at Scale in Production with kubectl debug
52mApplication-Level Debugging and Profiling: Gaps in the Tool Ecosystem
39mHow to Use Common Investigation Practices in Troubleshooting
45mDebugging Production: No Re-deploys, No Downtime, No Risk
31mObservability driven development