How To Finish What You Start: Lessons From Actually Shipping..
summary
A full-permissions overhaul lands safely in production: a Rails API and React front end move from old logic to a new Pundit authorizations implementation by shipping many small shippable pieces behind feature flags and backfills. The team maintains old and new systems, syncs data, backfills, tests with the flag on, flips it on in prod, and flips it off to mitigate bugs. Outcome: completed refactor, measurable teardown (lines removed), and zero emergency page incidents.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:15Ruby community love
- 2:20Unfinished refactors problem
- 5:09Refactors harder than they seem
- 7:15Champions and planning needed
- 9:01Know how you’ll ship
- 12:13Maintain two systems
- 16:43Feature flags and rollback
- 17:04Break into small shippable pieces
- 18:50Avoid distractions and side quests
- 21:38Cleanup after refactor
- 22:41Refactor completion celebration
- 23:44Don’t go it alone
- 25:07Key takeaways
- 27:13Closing and call to action
related talks
28mBreaking Rules to Ship Products: A Beginner's Rails Journey
34mShitlist-driven development and other tricks for working on large codebases
37mReal Developers Ship (a.k.a Tenets for Software Delivery)
25mIf You’re Not Shipping, You’re Not a Leader
04mInterview with Swizec Teller
30mShipping Through Chaos: Engineering Resilience Across Borders
29mBoot the backlog: Optimizing your workflow for dev happiness
30m10 Ways to Improve How You Ship Software