Death by a thousand commits
summary
A Rails codebase at Clio is eating performance and developer velocity via N+1s and accumulated dead code so the team builds specific tools: a jit preloader that cuts database time from spikes of two to four minutes down to ~30 seconds and halves the 95th percentile and triples the 99th percentile of requests a dead code detector that allows deleting ~300 controller actions and ~1,000 methods after a month of production data add marginalia plus ActiveSupport attributes to trace slow SQL and use RuboCop and a shitlist to block bad patterns like unwrapped Tempfile usage
AI-written summary · about
chapters (11)
- 0:00Start
- 0:14Pain Free Rails 66 Deployments
- 0:41Transforming the practice of law, for good
- 1:27Technical Debt
- 7:37Automate the debt away
- 15:41Clean up code you don't use
- 18:51dead_code_detector
- 19:20coverband
- 23:29marginalia
- 27:18Make it easier to keep the lights on
- 34:05Keep the bad patterns out
related talks
30mSilent Killers: Lessons from the Brink
31mAn Optimistic Proposal for Making Horrible Code... Bearable
34mShitlist-driven development and other tricks for working on large codebases
57mFuture of Developer Acceleration with Rails- 34mShitlist-driven development and other tricks for working on large codebases
28mRESCUE SQUAD: Rails Edition!
40mOptimize for developer speed
17mRewriting Code and Culture