Components, patterns and sh.t it’s hard to deal with
summary
The claim is concrete: reuse succeeds when boundaries and responsibilities are explicit. Examples come from production code (mustache, BEM, tiny lifecycle JS) and evaluate strategies: class name injection is maximally flexible but fragile and opaque; BEM modifiers or specialized modifiers preserve semantics yet can bloat and encourage premature variants; parent wrappers or spacing classes shift layout responsibility; exposing component props to expose gives controlled flexibility but requires careful API design. These approaches trade safety for flexibility.
AI-written summary · about
chapters (16)
- 0:00Start
- 4:08Disclaimer
- 5:08Lost in Translation
- 5:42Modular design
- 5:53Context
- 7:242013 - 2015
- 8:21Atomic design
- 9:09Web components
- 9:28Pattern Library
- 11:53The issue
- 14:45What really doesn't
- 22:23What works
- 28:33Learn what the pattern your are building is supposed to be
- 28:44Get involved early
- 28:54Talk to people
- 29:10and remember that...
related talks
26mComponents, 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
35mAdvanced patterns in building React Components
40mCommon Component Decomposition Pitfalls (And How To Avoid Them!)
30mReusability: Sharing Components
10mCrafting Accessible Components for Component Libraries
40m“A Working Theory of Components”