Saving Sprockets
summary
A major maintainer leaves a project with over 44 million downloads and more than 70% of commits concentrated in one person so the team documents concrete fixes: adds a deprecations branch, splits a 105‑method God object into helper classes, writes guides in the source tree, lands Windows tests and a merged Sprockets Better Errors patch, and uses tools like CodeTriage plus uglify js and source‑map tooling to validate source maps; progress is real but source maps remain partly unfinished and need actionable bug reports and example app reproductions.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 3:32Statistics
- 4:16What should we do
- 5:36Losing a maintainer
- 7:23Rules
- 9:00Actionable Feedback
- 9:43Be Honest
- 10:50Maintainers
- 11:45Commit Messages
- 14:30Example Apps
- 15:26Challenge
- 18:17Documentation
- 20:19Pat Diana
- 23:12Same Code Real Talk
- 24:13Better Errors
- 25:14Deprecation
- 26:42God Object Problem
- 28:19God Object Solution
- 29:48Respecting Commitment
- 32:43Bug Driven Development
- 33:55Source Maps
related talks
28mSaving Sprockets
31mHow Sprockets Works
37mHow Sprockets Works
36mWorking Compassionately with Legacy Code
34mSurviving the Big Rewrite
41mExploring the History of a 12-year-old Rails Application
24mPropshaft and the Modern Asset Pipeline
20mMaster the Rails Asset Pipeline: Best Practices for Apps & Gems