Lessons in Managing Technical Debt
summary
Teams migrate a messy multi-framework app to React with a gradual DOM‑level rollout, adopt React Testing Library after dropping Enzyme, and fold tests into feature work so coverage grows instead of rotting in the backlog. Performance fixes use IntersectionObserver, code‑splitting and lazy/Suspense with feature flags for safe deploys; bundling drops from six JS files to three and shaved off four megabytes saving about four seconds of initial load. Partial TypeScript migration occurs, and build‑time fitness checks are added to prevent regressions.
AI-written summary · about
chapters (8)
- 0:00Technical debt intro
- 2:28What technical debt means
- 4:35Types of technical debt
- 6:44Reckless vs deliberate debt
- 13:07Prudent deliberate case study
- 16:42Reckless inadvertent challenges
- 21:48Prudent inadvertent lessons
- 24:21Unknown unknowns in debt
related talks
35m팀장님 우린 내일부터 React+ TypeScript로 갑니다
57mBuilding Scalable, Maintainable Apps Using TypeScript and React
42mIntegrating React Into Legacy Projects
17mHow to deal with technical debt in fast-paced environment
31mLessons learned migrating complex software
32mThe How, What and Why of Migrating to ReactJS
21mMigrating critical apps to React
28mBack to React: The Story of Two Apps