Debugging debugging; why we must approach debugging differently
summary
Seventy five percent of developer time goes to bugs so the claim is if debugging improves feature output rises. Concrete fixes include 75% of developer time, a mandate to adjust sprint backlogs when bugs arrive, a clear bug prioritization method, and furnishing tickets with logs and repro steps. Tool work focuses on a cloud-native toolbox that supports live in-cloud debugging, integrated SDKs and monitoring so teams get usable data without being swamped.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:52Developers do a lot
- 1:52Survey
- 2:48Bugs
- 4:07Debugging
- 5:00Tools
- 5:30Solutions
- 5:53People
- 8:33Processes
- 10:23Tooling
related talks
01h 05mBack To Basics: Debugging Techniques
37mDebugging Without Borders
20mDebugging: Techniques for Uncertain Times
01mWho else codes for six minutes and debugs for six hours?
38mDebugging Embedded Linux
19mApp Engineers and QA Team Tackle Improving Debugging Features!
10mBeyond “try harder”: Effective strategies to tackle bugs
36mDebugging War Stories & Strategies to Survive