Principles for Scaling Frontend Application Development
summary
Six concrete principles with examples and outcomes decide whether to watch: move to a monorepo migration to remove npm private-module churn, prefer co‑located styles like Tailwind so CSS can be safely deleted, keep data fetching in the render tree (Next.js 13 app router) not hoisted to avoid hidden calls and cost, always migrate incrementally and use AST automation cautiously (Google’s Rosie pattern), encode rules as external allow‑lists and owners, and eliminate version skew by serving the exact backend version for a client so server actions behave deterministically — Vercel builds and experiments are already proving these work.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:47Backstory
- 3:27Google vs 2023
- 4:31Scaling Beyond Yourself
- 5:56tearing down the barriers
- 6:49private modules
- 8:09deleting code
- 8:41code bases
- 9:52data fetching
- 11:09migrate incrementally
- 13:25lint rules
- 13:58comments
- 14:31technical debt
- 15:06getting better and not getting worse
- 16:41Embrace lack of knowledge
- 17:36Application design opinions
- 19:19Eliminate systematic complexity
- 19:50Version SKU
- 22:32QA
related talks
27mScaling Your Front-End in a Realistic Way!
19mPatterns for Large Scale Vue.js Applications
50mOne Frontend App to Rule Them All 💍🌋
39mScaling Frontend Development
58mAlways crashing in the same car (the state of front end web development in 2022)
30mMicro Frontends in React — a State of the Art Approach
34mNavigating the Hype-Driven Frontend Development World Without Going Insane
40mScaling Frontend Development