Using Metrics to Take a Hard look at your code
summary
Shows concrete tooling and outcomes: runs code coverage, flog and cyclomatic tools (securu), and source control churn, then aggregates them with MetricFu aggregates coverage, flog, and churn into nightly reports. Gives thresholds for flog (0–10 safe, 21–60 review, 100+ danger) and highlights a real case where a DemLein method has flog score 155 and a broken apostrophe s discount that refactoring reveals and fixes. Warns metrics get gamed and must be team‑owned not manager‑enforced.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:14Lone Star Ruby Conf 2008
- 3:07So how do you down on crappy
- 5:28Why? • A pair can get excited and egg on
- 9:26What's a goc coverage numb
- 11:12In summary
- 12:46Complex Measurem
- 17:07Flog is Opinion
- 33:22Refactoring com methods yields benefits
- 34:34Why inject suc
- 36:30Consider the methods
- 38:17Explain Yours
- 41:03Source Control
- 44:11What Code Me can do for yc
- 46:54Metrics are not a and Forget' oper
- 51:18Bonus Slide: He
related talks
41mCode Metrics Q&A
01h 01mFinding Metrics that matter and using them safely
26mEngineering metrics, minus the creepiness
36mMetrics - What's your code actually doing?
05mMetrics That Matter
23mYou Get What You Measure—Why Metrics Are Important
31mMaking sense of frontend code with forensic techniques
35mEscaping The Tar Pit