The art of clean code
summary
Claims that maintenance eats ~2/3 of project cost and reading consumes ~25–30% of effort lead to concrete fixes: use RapidClipse or generators to write less, run Checkstyle/SpotBugs/SonarQube to eliminate 20,000 warnings (or the worse permanent 10 warnings), prefer JSR-310 date APIs to ambiguous methods, delete commented-out code, apply an automatic formatter to avoid brace bugs, improve exception messages with bounds, and do short frequent peer reviews to keep the codebase near zero warnings.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:35Context
- 1:37Why clean code
- 4:11Write less code
- 6:41Writing clean code
- 8:44General story
- 9:43Warnings
- 13:06Costs
- 13:59Code examples
- 19:21Commented out code
- 21:26Code formatter
- 24:13Style guide
- 27:43Hangarian notation
- 29:13Comments
- 33:18Error Messages
- 35:28Reviews
related talks
40mAssuring top-notch code quality in the Java Universe
43mClean code, is it really worth it? A story about monsters and...
25mClean Code, is it really worth it?
43mClean Code: Be The Hero
25mBest Practices for Writing Clean and Maintainable Codes
45mCracking the Code Review
43mCracking the Code Review: from Guesswork to Automated Guidance
59mTechniques for writing high-quality code