Why Design?
summary
A five‑minute condensation of a three‑hour deck claims design must solve problems not just express emotion and that one clear concept beats many guesses. It steps through actual tools and models: RGB vs CMYK vs RYB, explains primary → secondary → tertiary mixes, and names color schemes like monochromatic analogous complementary. It shows removing unnecessary lights and color during execution and ends by asking developers to study design theory and practice for better collaboration.
AI-written summary · about
chapters (5)
related talks
23mLearn Enough Design to be Dangerous
36mLearn Enough Design to Be Dangerous
54mDesign for Non-Designers from a Non Designer
46mMastering visual communication for software design
38mDesign for Non-Designers
43mRethinking Colors in Design Systems: A CSS Approach to Idiomatic Design
49mHow to Speak Designer
38mDesign for Developers