Design Book for Developers
This book is really inspiring for me.
However, a few days ago, our CTO picked it up and said, “The illustrations are so ugly, how can you call this design?”
Oops.
But it reminded me of the book “C++ Primer” that I read in college. At that time, I thought it was just okay, but it received a high rating on Douban.
So, it’s really important to encounter the right book at the right time.
I had already transitioned from C to C++ for some time and was using MFC, so I couldn’t really be considered as part of the “everyone” category anymore. It’s normal not to find it enlightening.
In my personal opinion, the purpose of this book is not to turn you into an expert, but rather to target those who have never paid attention to design or those who want to get started but don’t know where to begin.
Therefore, the book provides comparisons between no design and adding some basic design elements, which may not be appealing to experts.
- Four principles:
- Proximity
- Alignment
- Repetition
- Contrast
- Color
- Complementary
- Triadic
- Split-Complementary
- Analogous
- Dark and Light
- Fonts
- Oldstyle
- Modern
- Slab serif
- Sans serif
- Script
These basic points may be observed by someone who has never done any design, but they are usually not connected in a systematic way.
Once the human brain learns something, it cannot go back to the state of not knowing or simulate the state of not knowing. This is the curse of knowledge, as mentioned in the beginning with the “Joshua Tree” analogy.
So, any developers interested in design should start reading this book quickly.
Translated by gpt-3.5-turbo