"You Can't Miss What You Can't Measure"
summary
Argues that specific metrics guide real work not feelings: static analysis plus dynamic coverage exposes pain, churn pinpoints volatile files, and complexity predicts breakage. Demonstrates tools: turbulence plotting complexity versus churn (finds a model with complexity ~1600 and churn ~1000), uses flog and flay to locate high-scoring methods and duplicated email logic, extracts a service object and shrinks complexity, and wires up code climate/metric_fu and ActiveRecord graphing to map and monitor the codebase.
AI-written summary · about
chapters (4)
related talks
01h 06mKeynote - THE MISMEASURE OF SOFTWARE
29mYour Metrics Are Lying: How to Stop Reporting and Start Learning
40mEscaping the Tar Pit
34m"Escaping The Tar Pit"
43mTo Measure or Not to Measure? That Is the Question
39mTest Metrics – a thread or a threat
40mTesting Software Architecture
02h 44mMeasure, don’t guess: benchmarking stories from the trenches