Clean as You Code Your Projects
summary
Advocates a "Clean as You Code" rule: never merge code that fails quality gates and fix issues immediately. Uses SonarLint in the IDE and SonarQube/SonarCloud in CI to enforce rules, automatic fixes, and block deployments if coverage/quality gates (targeting ~80–95% test coverage) fail; presents metrics showing developers spend ~40% of time on debt, ~60% feel blocked, and ~20% of code is rewritten yearly, so gradual cleanup yields measurable quality improvement.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:06Clean Code goal
- 3:33Clean Code Taxonomy
- 8:06Non-compliant code examples
- 10:54Clean Code benefits
- 13:24Why code isn’t always clean
- 17:57Clean as You Code approach
- 21:33Practical implementation
- 27:54Sonar tools for Clean Code
- 33:14Conclusion
- 34:00Q&A
related talks
06mKeynote: Thrive with Clean Code
33mBuilding Code Quality
43mClean code, is it really worth it? A story about monsters and...
43mBuild in Quality
25mClean Code, is it really worth it?
42mThe art of clean code
29mManaging the code quality of your project. Leave the past behind: Focus on new code.
46mClean Code in AI era