Lessons for frontend development at scale
summary
Jira moves to a React-based SPA with over 1M+ lines of JavaScript and ~300 total contributors ~200 monthly, and lessons focus on concrete practices: treat UI features as composable components but rethink micro front-ends because the browser shares runtime; migrate from inside-out to outside-in to avoid big-bang rewrites; codify ownership in packages so runtime errors map to teams; enforce conventions with custom ESLint rules and an open-source tool called Stricter to automate consistency.
AI-written summary · about
chapters (7)
- 0:00Intro
- 4:08Decomposition
- 9:32Dont Big Bang
- 12:03Vertical and Horizontal
- 14:35DevOps
- 19:43Being opinionated
- 21:28Automation
related talks
22mDecomposition and beyond: frontend engineering at scale
31mLessons from 5 years of UI architecture at GitHub
25mThe tragedy of scale
26mHow to rewrite enterprise application into React ...
26mFrontend At Scale - Experiences Using React In A Large Organization
32mJavaScript at Scale by Stephanie Siaw (Eng) | JSConfAM19
43mRethinking SPAs: web-native apps
16mSPA at Scale