About the "occupational disease" of designers
|
I always feel that designers are the most sensitive and emotional people in the world. I don't feel any superiority when I say this, just like I think programmers are the most logical group of people in the world.  If you accidentally knock over a cup of Coke and the cola spills out and stains your clothes, (designers) often think, how can we design the cup so that it won’t knock over? Or if the Coke is knocked over it won’t spill? Or is there a fabric that can avoid getting dirty (non-absorbent is just a common practice)? When shopping, if you don’t have anything else in your mind, you will involuntarily pay attention to the world. For example, why are the lights arranged like this? Why is the light blue? How should it be arranged? What color should it be? When you see a box, you wonder why it is opened like this? Is there a better way to open it? Do I need to open a small window in the box? These questions may all be a split-second intuition. Just like a financial analyst's sensitivity to numbers. Graphic designers have intuitive responses to color, size, and shape, while interaction designers pay special attention to usage process and ease of use. When talking about these things with friends who are not in the same industry, they often sigh: Isn’t this very tiring? My answer is no, it’s just intuition, and it’s also a way to train your thinking. The daily experience photo group on Flickr is basically a perfect presentation of "occupational disease". From those pictures, we can see the sensitivity and pickiness of the designers... (For well-known reasons, you may need to use an agent to access this group of pictures) Sometimes thinking about these questions does not necessarily mean getting a correct answer. Otherwise it would be really tiring. If you can figure it out, let it go; if you can’t, just let it go. And when you encounter a similar situation in the future, it will be easy to associate it with the past. A designer's sensitivity is an instinct. So I often say that designers are like inventors (and they should be inventors). They discover problems from details and then solve them. |
<<: Understanding of the synchronous or asynchronous problem of setState in React
>>: How to set up a shared folder on a vmware16 virtual machine
Recommend
jQuery plugin to achieve image suspension
This article shares the specific code of the jQue...
Solution to the problem that VC6.0 cannot be used when installed on WIN10
VC6.0 is indeed too old VC6.0 is a development to...
Zookeeper unauthorized access test problem
Table of contents Preface Detect Zookeeper servic...
CSS3 to achieve simple white cloud floating background effect
This is a very simple pure CSS3 white cloud float...
The most detailed installation and configuration of redis in docker (with pictures and text)
1. Find a suitable version of redis for docker Yo...
Analysis of slow insert cases caused by large transactions in MySQL
【question】 The INSERT statement is one of the mos...
Example of how to build a Harbor public repository with Docker
The previous blog post talked about the Registry ...
Some suggestions for improving Nginx performance
If your web application runs on only one machine,...
Several ways to manually implement HMR in webpack
Table of contents 1. Introduction 2. GitHub 3. Ba...
The reason why MySQL manually registers the binlog file and causes master-slave abnormalities
1. Source of the problem A friend @水米田 asked me a...
VUE render function usage and detailed explanation
Table of contents Preface The role of render Rend...
10 key differences between HTML5 and HTML4
HTML5 is the next version of the HTML standard. M...
SQL Optimization Tutorial: IN and RANGE Queries
Preface "High Performance MySQL" mentio...
Two ways to implement text stroke in CSS3 (summary)
question Recently I encountered a requirement to ...
Detailed explanation of the differences between similar tags and attributes in HTML
【1】<i></i> and <em></em> ...