Escaping The Tar Pit
summary
Uses SimpleCov to get statement coverage (example 82%), and RubyCritic (Flog/Reek) to score complexity and smells, then combines them into a Skunk stink score that penalizes low coverage. Outputs a sorted list of stinkiest files, a stink-score average, and diffable branch comparisons (claiming e g +10% improvement versus master). Recommends refactoring files with ~60%+ coverage first, using Coverband to find dead code, and ships Skunk as open source to automate the workflow.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:13Escaping The Tar Pit
- 1:25Founder & Software Engineer
- 3:26Chapter 1: The Tar Pit
- 8:03Part 1: Avoiding the tar pit
- 8:54How can we quickly assess code quality?
- 9:24Open Source Gems Static code analysis
- 10:12What is software quality anyway?
- 10:31"The degree to which a system, component, or process meets implicit and explicit requirements." IEEE
- 19:49Are you getting into a tar pit, is it a dumpster fire, or have you found a project which is easy to maintain?
- 21:15Files which lack tests should be penalized
- 21:59foo.rb and bar.rb are equally stinky
- 28:44Churn vs. Complexity is not enough to prioritize
- 32:42Code Coverage; Complexity; and Smells
- 33:23Your compass to get out of the tar pit
