Clean Code, is it really worth it?
summary
Claims that poor-quality code costs $2 trillion in the US (2022) and steals about four days per month per developer; shows telemetry covering 1.8 billion issues with top defects: high cognitive complexity, unused code, commented-out code, lingering TODOs and common security smells. Demonstrates free tools SonarLint SonarQube SonarCloud and practical fixes: try-with-resources, prepared statements, Java records and switch expressions, cognitive-complexity metrics, and a Clean As You Code (CAYC) workflow that targets new code so cleanliness improves incrementally.
AI-written summary · about
chapters (11)
- 0:00Why clean code matters
- 3:48Poor quality code
- 6:39Cost of poor code
- 8:51Clean code principles
- 10:58Top code issues
- 14:57Security and design flaws
- 18:12Refactoring complexity
- 20:42Static analysis tools
- 22:08Clean as you code
- 23:12Killing poor code
- 24:21Tooling and final recommendations
related talks
43mClean code, is it really worth it? A story about monsters and...
06mKeynote: Thrive with Clean Code
46mClean Code in AI era
42mThe art of clean code
33mCode Quality Metrics to Measure and Quantify Quality of Code
44mClean as You Code Your Projects
43mClean Code: Be The Hero
46mCode Quality in the AI era, needed more than ever