The Future is in Pieces
summary
Argues that modular UI wins: adopts SMACSS/BEM/Atomic Design, uses Sass, Pattern Lab and mustache-style templates, and pushes toward Web Components while noting element queries remain a JS-only workaround. Cites painful legacy examples—a single 16,000-line CSS file—and concrete fixes: extracting a refactored button module, building a shared style guide/component library at Shopify and Yahoo, and using visual regression and template-driven components to test states and locales.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:25Coding like it's 2003
- 3:59Wait what?
- 11:10Categorization
- 17:38Naming Convention
- 21:39All the things
- 25:41React Components
- 26:35Web Components
- 35:31Patterns
- 36:50The Future is in Pieces
related talks
32mModular & reusable front end code
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
23mComponents, Patterns And Sh*t It’s Hard To Deal With
26mComponents, Patterns and Other Not-So-Simple Things to Manage
37mFuture-Proof CSS
41mThe power of progressive enhancement
40m“A Working Theory of Components”
24mDesigning Components for Fun, Profit and Sanity