Clean code, is it really worth it? A story about monsters and...
summary
Poor quality code costs $2.4 trillion in the US and developers spend 4 days per month fixing bugs, so the recommended approach is Clean As You Code with IDE linters and CI quality gates (example tools: SonarLint / SonarQube). Static analysis finds millions of issues — cognitive complexity flagged ~14M times, many unused assignments, parameters, TODOs and empty methods — and rule sets include ~665 Java rules plus ~100 infra rules. Focus on new code, tune false positives, and enforce small, incremental fixes via linters and CI.
AI-written summary · about
chapters (13)
- 0:00Introduction to clean code
- 3:19Cost of poor quality code
- 9:03Introducing the monster Porky
- 12:17Hero’s daily struggles
- 14:24Clean Code Warriors principles
- 17:13Fighting tricks against Porky
- 21:48Most detected code issues
- 25:22Security challenges
- 27:07Common Java pitfalls
- 30:00Cognitive complexity explained
- 32:08Right approach to clean code
- 36:43Clean as you code strategy
- 39:31Conclusions and final thoughts
