How to Debug - Lessons Learnt from 10 Years of Spring Boot
summary
Ten years of Spring Boot yields concrete debugging habits: maintain a tiny reproducer (start.spring.io), paste full stack traces into a stack-trace console to jump to guilty lines, use GitHub permalinks (press Y) and detailed commit messages, and prefer conditional breakpoints and hit counts when stepping through code. The project records 4,395 bugs closed, many fixed by one-line changes plus tests, some requiring upgrades (Docker compose flag or library bump) or revealed by locale-specific bug (Turkey).
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:31Defining bugs and debugging
- 2:15Types of bugs
- 3:44Reporting bugs effectively
- 5:03Creating a minimal reproducer
- 8:06Troubleshooting via reproduction
- 9:27Bug report formatting
- 12:11The life of a maintainer
- 13:21Git and GitHub fundamentals
- 15:09Importance of commit messages
- 17:58Using stack traces for debugging
- 18:56Writing tests to fix bugs
- 22:12Advanced breakpoint techniques
- 27:34Debugging in memory
- 30:55Debugging third-party code
- 33:23Environment specific issues
- 36:43Locale-based bugs
- 39:46Windows vs Linux differences
- 42:37Test pollution issues
- 44:17Handling library upgrades
- 45:53Summary and conclusions
related talks
57mHow to Debug Lessons Learnt From 10 Years of #SpringBoot
49mDas Boot: Diving into Debugging Spring Boot Applications
47m10 ways to get super-productive with Spring Boot
58mDebugging #Java
49mSpring Debugger New Power: Where Should I Click to Demystify Spring Boot Magic?
42mSpring Debugger: A New Way To Demystify Spring Boot's Magic
38mLearning from your bugs
49m10 Excellent Ways to Secure Your Spring Boot Application