Ecosystem or Zoo
summary
A talk about managing parallel work on design and frontend across dozens of interrelated systems that form a single ecosystem. It describes moving from ad-hoc development and repeated code to creating internal libraries (and making developers their own users), with some components released as open source, and argues why publishing OSS is important and beneficial.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:53Chaotic development problems
- 8:35First improvement attempt
- 14:36Reflection and new tasks
- 18:10Technology selection
- 19:35Designers' routine elimination
- 22:27Design and development collaboration
- 31:50Framework abandonment
- 35:45Results and benefits
- 45:18Q&A
related talks
39mThe Care of Software: Ethics and Ecosystems
30mDeciding between continuity and change in your Open Source community
46mBuilding & Managing Design Systems
29mEffective design and engineering collaboration
11mKeynote: The Impact of the Ecosystem
14mHelp, I'm an Architect for an Open Source Project!
38mDesign systems panel discussion
35mRipping Apart the Monolith