Migrating Safely to React
summary
PayPal’s send flow migrates incrementally: a weekend rewrite of the notes field lands and reduces files from two to one, the routing layer moves to React Router over three weeks, and a React container acts as a bridge to Backbone so old views keep working while new ones replace them. Redux is introduced for the data layer with logged actions that make state bugs visible and fixable, and AB tests plus staged rollouts validate each change.
AI-written summary · about
chapters (37)
- 0:00Intro
- 0:15Sightseeing
- 1:15Send Money
- 1:49Modern Stack
- 2:11B Testing
- 2:36Too many abstraction layers
- 3:59How did things get so bad
- 4:45Simple Made Easy
- 5:07Easy Solutions
- 6:05Sustainable Momentum
- 6:24The Takeaway
- 7:31The Narrative
- 7:57Move over one feature
- 8:37First page
- 9:04Second page
- 9:59Lessons learned
- 11:24Whats next
- 11:38What is the routing layer
- 13:22General wisdom with React
- 14:02ShowView function
- 14:38Load scripts
- 15:44React Send Layer
- 16:00Show Backbone View
- 16:16Show V View
- 17:08Migration Path
- 17:50Data Layer
- 18:14Models
- 18:46Redux
- 19:24Money Flow
- 19:41Calculator
- 20:16What Would Read
- 22:44New Features
- 23:25Optimization
- 23:40Michael Feathers
- 24:02Framework agnostic
- 24:34Utility
- 25:58Dont Make Us Suffer
related talks
21mMigrating critical apps to React
32mThe How, What and Why of Migrating to ReactJS
38mMigrating from PHP legacy code to React & Best Practices in React
31mLessons learned migrating complex software
10mHow to migrate 50,000 lines of code to React Server Components
28mLessons in Managing Technical Debt
40mHow I learned to love React
31mReact on Rails