RESCUE SQUAD: Rails Edition!
summary
A five‑step rescue plan for rotten Rails apps that delivers concrete actions: enforce style with RuboCop, capture coverage and cyclomatic complexity via SimpleCov & MetricFu on CI (Travis) and surface metrics in dashboards, ruthlessly delete low‑value tests and reduce code surface area, detect duplication with flay, keep Rails up to date, and fail the build on regressions. Claims: measurable drops in complexity and churn, higher actionable coverage, faster feedback loops and a codebase small enough to change without fear.
AI-written summary · about
chapters (16)
- 0:00Start
- 0:03ANCIENT CITY RUBY
- 7:55RAILS DERAILED
- 8:58CHANGING REQUIREMENTS
- 10:29PERCEPTION CHANGE IT!
- 11:44BEINGA POSITIVE INFLUENCE
- 12:19BROKEN WINDOWS
- 14:22EFFECTA CONSISTENT STYLE
- 17:07TEST COVERAGE
- 20:01CODE CLIMATE?
- 20:27METRIC OVERFLOW!
- 21:08DASHBOARD
- 22:09TESTS CAN BE TRANSIENT
- 24:01REDUCE THE SURFACE AREA
- 24:23IMPROVE INCREMENTALLY
- 25:41ALWAYS BE IMPROVING
related talks
41mRescue Mission Accomplished
20mWhat were they thinking?
33mSo You Want to Start Refactoring?
29mLessons From A Rails Infrastructure Team
23mEmbracing Code Quality with Rubocop
27mScaling Ruby Applications: Challenges, Solutions and Best Practices
40mInto the Heart of Darkness: Rails Anti-Patterns
33mRefactoring Towards Component-based Rails Architectures