Code Quality in Practice
summary
Code Climate reports that static analysis scales to over one trillion lines of code each day across 75,000+ repositories and 1,500 organizations, and finds practical lessons: prefer simple metrics like lines of code over opaque ABC scores, keep human reviews under 400 lines to catch defects, treat disposable prototypes as business decisions, tolerate localized Omega messes that only have inbound dependencies, and attack the real blocker—fear of breaking things—by investing in tests, CI, monitoring and code review workflows.
AI-written summary · about
chapters (9)
- 0:00Introduction and welcome
- 1:47Defining code quality
- 5:39Measuring code complexity
- 12:47Why older projects degrade
- 19:38Optimal pull request size
- 23:53When sloppy code is acceptable
- 31:04Why quality code is hard
- 39:26Overcoming code quality problems
- 40:12Q&A session
related talks
30mKeynote: Code Quality Lessons Learned
33mCode Quality Metrics to Measure and Quantify Quality of Code
38mCode Red: The Business Impact of Code Quality
18mBuilding a Culture of Code Quality
43mClean code, is it really worth it? A story about monsters and...
51mCode Red: The Business Impact of Code Quality
46mCode Red: The Business Impact of Code Quality
45mCode Red: The Business Impact of Code Quality