Spacecraft! The care and keeping of a legacy ...
summary
Uses a spaceship allegory to make concrete claims: avoid full rewrites unless metrics justify them, prioritize flaky and the 10 slowest tests, and aim to move a 1 to 0.2 code‑to‑test ratio toward 1 to 1. Shows specific tooling and practices: railstats, simplecov, rails-erd, plus churn and complexity analysis (skunk/flog/codeclimate) to find hot spots. Describes incremental fixes, recovering institutional knowledge, instituted team agreements (two approvals, monthly retros) and reports that the approach restores confidence and keeps the app running.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05Despair in a Galaxy not very far away
- 3:13Black hole of rewrites
- 5:17Assessing spaceship
- 8:28Fixing flaky tests
- 11:39Unknown ship parts
- 13:47Recovering knowledge
- 17:40Socializing knowledge
- 19:47Teamwork on legacy
- 23:18Legacy care sum
