Keynote: Code Quality Lessons Learned
summary
Code Climate claims that static analysis really scales — 70,000 repositories analyzed daily — and that practical findings beat fancy metrics: ABC and cyclomatic complexity exist but lines of code often gives a clear, actionable signal. Human reviewers stop finding defects past about 400 lines per pull request. The surprising root cause of decay is fear of breaking things, and automated checks plus small iterative changes are the concrete antidotes shown to work.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:1980,000+ Repositories
- 1:32500+ Organizations
- 1:561. What is code quality?
- 2:50Code quality has many meanings
- 4:06Make sure you're team is on the same page about your goals.
- 5:10What's the best way to measure complexity?
- 8:40Use a metric that resonates for your team.
- 9:23If you can't decide, use Lines of Code.
- 11:27Why are older projects harder to maintain?
- 12:19Sloppy code is self-reinforcing
- 14:04Code quality is a moving target
- 16:10What's the optimal size for a pull request?
- 18:23Keep pull requests under 400 LOC.
- 19:51When is sloppy code not a problem?
- 20:16Proving a hypothesis
- 21:32Build the first one to throw it away.
- 24:10What is the biggest enemy to clean code?
- 25:46Changing requirements?
related talks
01h 00mCode Quality in Practice
06mKeynote: Thrive with Clean Code
18mBuilding a Culture of Code Quality
43mBuild in Quality
35mThe Code Quality Advantage How Empirical Data Shatters the Speed vs Quality Myth
45mCode Red: The Business Impact of Code Quality
51mCode Red: The Business Impact of Code Quality
33mBuilding Code Quality