What It Takes to Upgrade a Tech Stack for 70+ Developers: Firsthand Experience
summary
A large search UI migrated from legacy BEM/vanilla JS to React + TypeScript over about two years with a small core team and ~70 developers involved. Instead of a full rewrite they embedded a parallel runtime into production, ported a representative feature first, kept reusable components in the main repo, and taught teams via TypeScript controllers and live examples to enable an incremental rollout; React reached roughly 50% of SERP and about half of product teams adopted the new stack.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 3:55Motivation for upgrade
- 5:23Critical path concept
- 7:35Parallel runtime approach
- 8:39Pilot feature selection
- 10:51Preserving conventions
- 11:37Gradual team immersion
- 12:43Expert knowledge sharing
- 13:28On-the-job learning
- 14:32Preparation for training
- 15:56Component reuse challenges
- 18:04Support mechanisms
- 19:28Feedback and prioritization
- 20:35Metrics overview
- 22:25Progress tracking
- 23:49Key takeaways
- 25:58Q&A
related talks
22mThis is Not Just Any Transformation; This is a Transformation
28mRefactoring Your Way Up
12mDriving technical excellence from the top: A case study in uplevelling
29mHow to change mindset of coworkers?
32mRebecca Murphey - SeattleJS Conference 2017
10mTaking the Next step
31mBuilding an Enduring Culture of Engineering Excellence
28mAdopting New Technologies in a Modern Enterprise