Clean Code, Two Decades Later
summary
Covers the most damaging code smells of 2023 with concrete refactor recipes and live-coding examples: identifies long methods, nested lambdas, accumulator loops, rampant longs/strings and 4+ parameter signatures, and shows exact fixes like guard clauses, extracting named functions for lambdas, and introducing value objects for IDs. Shows when to prefer streams vs loops, why mutating state in stream pipelines is a smell, how many reviewers/programming practices reduce defects, and practical steps teams can apply tonight.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:50What is clean code
- 3:20Clean code evolution
- 4:25Code smells impact
- 11:11Monster methods
- 12:13Deeply nested lambdas
- 16:51Classes with too much code and responsibilities
- 18:57Primitive obsession
- 21:04Feature envy
- 22:50Strong types prevent mix-ups
- 25:19Functional programming
- 27:45Higher-order functions
- 29:11Immutable objects
- 31:40Streams and mutation
- 34:11For loops and optional
- 36:26Performance myths
- 39:16Functional purity
- 43:10Variable naming
- 43:54Expression functions
- 45:20Reactive programming
- 46:05Dead code cleanup
- 47:29Feature flags
- 49:13Code cleanup
- 50:38Over-engineering
- 52:26Legacy quirks
- 53:52Summary
- 54:35Call to action
