Components, Patterns and sh*t it’s Hard to Deal with
summary
Claim: pattern libraries often devolve into scattered overrides that break refactoring and maintenance. Evidence: examples from 2013–2021 using React, BEM-style CSS, class name injection and modifier classes, plus specialized components and styled-components as alternatives. Built artifacts include dialog components adapting to parent size and icon components accepting width/height props; some solutions work but increase API complexity. Operational note: visual regression testing is rare — only two raised hands — so many regressions go unnoticed. Practical tradeoffs are the focus.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:41Who am I
- 5:41Backstory
- 7:20Web Components
- 8:58Pattern Libraries
- 12:23Class Name Injection
- 15:53Specialized Patterns
- 17:43Redefine the Problem
- 19:03Space Between Components
- 20:43Open Components
related talks
30mComponents, patterns and sh.t it’s hard to deal with
23mComponents, Patterns And Sh*t It’s Hard To Deal With
26mComponents, Patterns and Other Not-So-Simple Things to Manage
34mAdvanced React Component Patterns
10mCrafting Accessible Components for Component Libraries
44mWriting good components
24mDesigning Component API
24mDesigning Components for Fun, Profit and Sanity