The Tale of Two Teams
summary
Two product teams start with messy, decade‑old code; one integrates a new frontend incrementally, the other attempts a full rewrite and stalls. The successful team ships multiple features fast by using Ember CLI, relying on linkable URLs to move between apps, and embedding legacy pages via iframe + postMessage while keeping state in Ember Data. Result: shipped value, paid down technical debt; the Big‑Bang rewrite loses time and repeats work.
AI-written summary · about
chapters (9)
- 0:00Intro
- 3:10The Story
- 8:32The Downside
- 12:07Onboarding New People
- 13:37Ember CLI
- 13:57Workflow
- 15:20Production ready
- 16:55Derailed
- 20:07Adopting Ember
related talks
35mPanel: Ember – Why and Where?
28mModernizing a Massive Monolith
22mUsing Ember to Make the Seemingly Impossible Easy
22mUsing Ember to Make the Seemingly Impossible Easy
26mReuse, Recycle: One Team’s Journey from Projects to Products
25mThe Chirpolith: Successfully Migrating a Messy App to Ember
49mKeynote Part 1
36mPanel: Ember at Scale