Break free from maintenance hell with Clean Code
summary
Maintenance eats roughly two thirds of lifecycle cost and reading code costs about 30 percent, backed by 15 years of examples and practices. Practical fixes include using the Java compiler plus Checkstyle/FindBugs/SpotBugs/Sonar to surfacing 20,000 warnings and avoiding the trap of zero warnings vs 10 warnings, remove commented out code and use meaningful APIs instead of magic numbers, enforce a use formatter and braces convention, prefer short frequent reviews, and aim to shrink the zone of chaos so late Friday firefights become rare.
AI-written summary · about
chapters (21)
- 0:00Intro
- 3:17Development and Maintenance
- 3:54Distribution of costs in the software life cycle
- 4:56Don't write code
- 5:50CSV Import?!
- 6:36code or use?
- 7:47Copy & Paste vs. Reuse DRY (Don't Repeat Yourself)
- 8:33Design Pattern
- 9:23What is clean code? Code with no compiler errors?
- 10:26What is not clean code?
- 14:31Zero Warning Policy Warnings indicate problems
- 15:18Costs of changes / bugs
- 16:23Structure and naming - Make the API unambiguous
- 21:49What about old code commented out ?
- 24:06Code conventions: structure
- 26:48Style Guide?
- 27:16Swap in memory
- 30:25Code conventions: Style
- 32:14Comments
- 38:31Error messages
- 43:20Review Benefits Avoid Zone of Chaos
related talks
37mWe Hate Code - The !joy of Maintaining Dead Code
25mBest Practices for Writing Clean and Maintainable Codes
30mDoes Your Code Hurt?
57mThe Art Of Clean Code
29mClean Code in Practice
44mWe Hate Code: The !Joy of Maintaining Dead Code
51mTwelve Ways to Make Code Suck Less
36mWhy programming is fiendishly difficult and what we can do about it