Holy War between Designers & Developers
summary
Argues that inconsistent buttons, colors and five different "sources of truth" cause duplicate components and broken fixes, so teams build a documented component library with colors, spacing and atomic pieces, coordinate via tools like Zeplin Sketch Figma and even Abstract pull requests to sync design and code. Recommends starting small, iterating (do one solid version, not 25 variants), not blindly copying Material, and warns design systems are no silver bullet for tiny fast projects or teams that refuse to collaborate.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:10Communication problems
- 3:42Sources of truth and discrepancies
- 6:12What is a design system
- 8:18When design system isn't needed
- 9:42Implementing design systems
- 11:05Designer-developer collaboration
- 12:35Tools and team risks
- 14:24Conclusion
related talks
25mPanel discussion about design systems
34mDesigners, Developers, Let’s Create the Difference!
14mRethinking Designer-Developer Collaboration
29mEffective design and engineering collaboration
27mFoundations of Design Systems
46mBuilding & Managing Design Systems
47mA universal fusion of the team
39mDesigning with Components