Actionable insights vs ranking How to use and how NOT to use code quality metrics
summary
Shows concrete metrics, Python code snippets, and calculations for function length, cyclomatic and cognitive complexity, and a working memory score so you can reproduce numbers. Reports that the median function length ~5–6 lines and typical working memory ≈9 across popular projects. Uses repoanalysis.com and Sorcery tooling and a weighted aggregate like a maintainability index. Demonstrates a real rewrite that cuts cognitive complexity and warns that outliers persist and metrics can be gamed.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:01Overview
- 4:05Function Length
- 5:48Cyclomatic Complexity
- 10:55Working Memory
- 12:30Code Quality Metrics Matrix
- 13:31Compound Metrics
- 18:22Interpretation
- 19:32Refactor or rewrite?
- 20:44Recommended Usages
- 22:07Summary
- 23:01General
- 24:17What Code Quality Doesn't Measure
- 25:26Use metrics for
- 26:12Do not use metrics
related talks
33mCode Quality Metrics to Measure and Quantify Quality of Code
30mKeynote: Code Quality Lessons Learned
35mThe Code Quality Advantage How Empirical Data Shatters the Speed vs Quality Myth
46mCode Red: The Business Impact of Code Quality
29mManaging the code quality of your project. Leave the past behind: Focus on new code.
41mCode Metrics Q&A
49mIdentifying bad design in codebases, objectively…
51mDoes Your Code Measure Up?