It's About Systems
summary
Argues that front end work needs explicit systems thinking not accidental fixes and shows what that means in practice: a built pattern library from existing code that became a mess teaches why reductionist component breakdown fails without system boundaries. Defines a process: define the system and vision, create content templates, sketch and prototype in browser, use tools like Pattern Lab CSS slick Maps Ginger and its node variant nunu plus Handlebars or Sass macros, document standards and iterate until the components actually compose and scale.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:43break larger problems into smaller problems
- 1:29code from the inside out
- 1:40components & modules not pages
- 2:11agile, iterative, user centered development and design
- 4:38Tools change rapidly humans do not
- 4:50Systems Design is the application of Systems Theory
- 6:51too simple Reductionism
- 8:56science of wholeness Systems are
- 10:36self-regulating through feedback Systems are...
- 15:08good systems design takes times
- 18:25Vision Requirements Goals
- 22:24Content Templates
- 24:13Sketches Prototypes
related talks
15mWhy You Should be Building Design Systems and CSS Architectures
21mDesign Systems 101: The Developer Approach to Better Frontends
32mIntroduction to Design Systems
33mGet the core right and the resilient code will follow
35mDesign system - From a Developer Point-of-View
25mPanel discussion about design systems
38mDesign Systems Mastery: From Patterns & Principles to Product Excellence
27mFoundations of Design Systems