Assuring top-notch code quality in the Java Universe
summary
Argues that maintainability drives velocity and shows concrete tooling: enable the resource-close rule to catch streams that cause swap-filled production incidents, run SpotBugs, PMD and error-prone together to reduce false negatives, and use Spotless auto-fix plus an .editorconfig to eliminate formatting fights. Claims a combo of linters plus compiler plugins finds subtle bugs (short-to-int promotion, forgotten unlocks) fast, and recommends raising bus factor with pairing and strict, brutal code reviews.
AI-written summary · about
chapters (16)
- 0:00Introduction to code quality
- 2:01The ultimate quality in software
- 5:15Productivity and code quality
- 7:21Code reviews and professionalism
- 10:50Code style guides and conventions
- 13:45Resource management and leaks
- 16:16Bus factor and team knowledge
- 18:39Automated tools for quality
- 21:39Checked exceptions and best practices
- 23:27Formatting tools and consistency
- 27:24Error detection with tools
- 28:51Spotless and formatting fixes
- 30:20Line endings and cross-platform issues
- 31:48Technical debt and its impact
- 33:12Recruitment and team complexity
- 35:26Summary and maintainability
related talks
42mThe art of clean code
43mCracking the Code Review: from Guesswork to Automated Guidance
21mCode reviewing like a champion
59mTechniques for writing high-quality code
33mBuilding Code Quality
43mClean code, is it really worth it? A story about monsters and...
43mBuild in Quality
25mBest Practices for Writing Clean and Maintainable Codes