The art of investigating problems in software
summary
Shows a checklist of concrete techniques: use problem isolation to pin where UTF-8 corruption occurs across front end, services, and DB; capture network traffic with Wireshark to reveal an unauthorized error caused by Lerna version skew; attach a debugger to Maven to set an exception breakpoint and drop frame to find duplicate-module import paths in a 500+ module build; use strace-like tracing to see why Kanika’s drop kill capability fails when a daemon changes effective UID.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 1:09Enjoy debugging sessions
- 2:35Case one problem isolation
- 6:10Case two low level debugging
- 7:55Case three debugging Maven build
- 13:19Debugging with strace
- 15:50Key takeaways enthusiasm and courage
- 16:57Q&A session
