Building Code Quality
summary
Argues for measurable, incremental fixes: boy scout rule (leave code cleaner than found), stop introducing new slop, and follow two steps — assemble information and act. Recommends concrete tools and signals: build failures, static analysis, Jenkins and Code Climate scans piped to chat as early warning systems. Practices include one-on-ones, retrospectives, anonymous surveys, and hands-on group refactoring called team factoring to teach refactoring and prevent legacy-code spirals.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:19Building a Culture of Code Quality
- 1:24Presenting Problems
- 3:11Vicious Cycle
- 4:51Opposing Forces
- 10:58Fixing Any Problem
- 11:13Qualitative Data
- 13:18Quantitative Data
- 18:07Lunch and Learn
- 19:30Teamfactoring
- 21:28Early Warning Systems
- 24:59Language Error
- 25:22Painless Code Reviews
- 27:29Review Criteria
- 31:31Virtuous Cycle
related talks
18mBuilding a Culture of Code Quality
43mBuild in Quality
25mBest Practices for Writing Clean and Maintainable Codes
44mClean as You Code Your Projects
28mSome small steps for code, One giant leap for quality
51mReasons and Ways to Improve Code Quality
59mTechniques for writing high-quality code
11mTake back control of code quality