Balancing the General and the Specific at Massive Scale
summary
Presents a practical decision method for when to create shared UI: a formula comparing per‑service development and deployment costs against the extra unification cost, showing shared components pay off only with many consumers or much easier deployment. Recommends operational tactics including a layered design system with local overrides, team‑kit token inheritance for theming, a central Storybook, automated cross‑repo testing and release bumping, and strict backward‑compatibility rules.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:28Company scale context
- 3:14Why consistency matters
- 6:30Balancing general and specific
- 8:41Code reuse challenges
- 11:32Evaluating shared libraries
- 17:23Decision-making formula
- 23:06Technical balance solutions
- 26:59Design system layers
- 31:14Technology tools
- 32:01Q&A
- 44:58Summary
related talks
28mLet's talk about design systems
36mConsistency is Key - Working with a Design System
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
27mFoundations of Design Systems
27mAdvanced Design System Considerations
46mBuilding & Managing Design Systems
31mIncremental Design - A conversation with a designer and a developer
15mHoly War between Designers & Developers