Rewriting Code and Culture
summary
A Rails monolith gets carved into HTTP services by first pushing complexity into Ruby service classes, then replacing them with real APIs; releases move from hours between builds to a build under a minute and end-to-end tests ~5 minutes. The team rewrites pages one at a time (starting with the event page), deletes unused features and tests, ships the new site with no downtime, adopts continuous delivery and rewrite on master, and pairs designers and developers so the architecture actually speeds product velocity.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:07Dependency Graph
- 3:41Where To Start
- 4:00End Goal
- 4:47One Specific Goal for Your Rewrite Project
- 7:08Rewrite the Application on Master
- 11:55Fast Release Cycle
- 12:07Delete Tests
- 13:03Service-Oriented Architecture
- 14:16Cultural Changes
related talks
35mA Tale of Two Codebases
34mShitlist-driven development and other tricks for working on large codebases
31mAn Optimistic Proposal for Making Horrible Code... Bearable- 34mShitlist-driven development and other tricks for working on large codebases
13mShift left the proper way
40mOptimize for developer speed
27mMaintainable Ruby on Rails
24mHow to prevent a rewrite