The past and future of designing interfaces
summary
Cites a study showing 88% of spreadsheets have errors, argues auditing finds more mistakes rather than people making more, and treats UI work as input/output that must be exhaustively checked. Describes a proof‑of‑concept tool that stubs content, iterates component props (colors, counts, typography) and generates an automated state grid — a matrix of components × palettes — surfacing thousands of component states (even millions) so developers catch visual and data bugs earlier; demo works as intended.
AI-written summary · about
chapters (6)
- 0:00Introduction and welcome
- 3:57Computers as input/output systems
- 16:59Debugging and feedback loops
- 18:49Demo of component automation
- 24:10Collaboration and revolution
- 26:46Call to dream bigger
related talks
14mDesigning UIs without a UI designer
42mIndispensable Principles for Designing Complex User Interfaces
15mHoly War between Designers & Developers
29mDesigning with Code in Mind
53mLess look, more feel. Improving the user experience as a frontender
23mWriting is designing
42mBack to the Future: No More Static Mockups!
59mBetter Code: Human Interface