The Designers Are Coming
summary
Argues that designers now build, iterate and deploy usable web apps without handoffs because deployment is essentially version control: examples include push Heroku master, Capistrano and Hubot automations, and the 48‑hour prototyping of Rails Rumble. Shows measurable design wins: better retention from typography, grid systems and vertical rhythm applied via SASS templates, and clearer data with Tufte’s principles and Minard’s flow map. Claims developers must adopt measurable design rules or lose product influence.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:59Wazza
- 7:27Version Control
- 9:01Evolving Skills
- 13:01Time to Fight Back
- 14:17Eric Ries
- 21:26Grid Systems
- 25:11Practical Guide for Designing for the Web
- 26:37Underlining
- 27:29Edward Tufte
- 28:48Example
- 30:18Minimum Viable Change
- 32:54The Greatest Data Graphic Ever
- 35:16Dieter Rams
- 36:50Design is a science
- 37:45Our values are shared
- 38:29Conclusion
related talks
38mEnough Design
23mDevelopers, start designing!
31mIncremental Design - A conversation with a designer and a developer
57mDesign Engineering: The next era of Software Design
52mDesign Engineering: The next era of Software Design
37mAdding Design to DevOps
17mBlurring the line between designers and developers with Meng To
51mUX + Engineering: A Tale of Two Cities