"Escaping The Tar Pit"
summary
A concrete method for triage and gradual payoff: measure coverage with SimpleCov and runtime traces with coverband, compute complexity with flog (ABC metric) and smells with reek via RubyCritic, then combine them into a per-file StinkScore implemented in the open source tool skunk. Complex files with 0% coverage get large penalty factors while identical files with 100% coverage score far better. Reports show stink score average, let you delete unused files, pick refactor targets, or quantify a 10% improvement after a branch.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:14Tar Pit Symptoms
- 8:48Assessing Quality
- 11:50Maintainability
- 12:41Code Coverage
- 17:38Churn vs. Complexity
- 20:36Coverage & Complexity
- 25:54Removing files
- 26:45Refactoring files
- 29:06Increasing coverage
- 31:40Stink Score
