Is clean code dead?
summary
Argues that clean code is under threat from delivery pressure, AI-assisted coding, fewer juniors and unclear ownership, and shows practical fixes: rename and extract a long order function into four focused functions to get ten unit tests and isolate bugs, replace magic numbers with constants, and adopt automated tests plus TDD/red-green-refactor. Recommends team agreements, code reviews and collaborative approaches like pair/mob programming alongside meaningful names and short focused functions to keep code maintainable.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:48What is clean code
- 3:38Clean code at risk
- 7:16Clean code still matters
- 10:51Practical clean code tips
- 16:35Automated testing importance
- 18:49Refactoring legacy code
- 21:25Team coding standards
- 24:19Conclusion
related talks
25mBest Practices for Writing Clean and Maintainable Codes
53mIntentional Code - Minimalism in a World of Dogmatic Design
29mClean Code in Practice
13mClean Code Matters
54mReadable Code: The Secret to Clean, Productive Software
43mClean Code: Be The Hero
25mClean Code, is it really worth it?
30mHot Garbage: Clean Code is Dead