The love and hate of a pixel, the troubles between programmers and designers

I didn’t intend to stir up the so-called conflict between positions until I saw such an article today. Yes, this is an article about the conflict between programmers and designers. The origin is this: a netizen asked a question in a community:

The developer refuses to restore the design according to the UI annotations. How can we make him understand the importance of accurate restoration so that he can modify the code?

When a development engineer repeatedly asks "What's the point of asking me to move 1px here? Why should I waste my time doing this?" and refuses to make changes, how can we make this developer understand and realize the importance of making changes?

Why do many visual designers in China have to chase engineers to modify those details that seem trivial or even trivial, but are still very important to designers, and list the problems one by one, but cannot get a positive response from the engineers? For example, I heard from a colleague that Frog engineers would develop their own software to check and modify the design restoration in order not to affect the work of visual designers.

What is the reason behind the difficulty in product design? Is it because the designer does not understand the code? Is it because of the aesthetic awareness of some technical personnel? Or is it the mentality of big companies or some other reasons? How to solve this situation? At what time or opportunity can it be solved?

Well, as expected, the top answer was this.

Due to space limitations, please copy the link to view the full text in your browser. http://zhi.hu/8lyF

Throughout the article, the author spared no effort to slander and ridicule the designer, and even changed the subject, writing:

For software development, the work of coders is necessary, while the work of designers is optional.

Even if no one does the design, the software can still be used. In fact, in today's flat world, many developers, such as iOS, have system default templates that are not good-looking, but they are not a rough house. But if no one writes code, then there is nothing to be gained.

The importance of the work determines who listens to whom. It's that simple.

Well, after reading it, the only feeling I had was, is this the mafia or is it just too self-righteous? If the user group determines the quality of the answer, I have no doubt about it. In addition to expressing a little bit of antipathy towards this community, I also want to write about my own thoughts and experiences on the relationship between designers and developers in reality.

First of all, let me state my position. I am a designer and I know a little bit about codes and products.

Origin: 1 pixel, should it be changed or not?

As a responsible designer, one pixel is not important to them. If they say it is not important, then Static Electric believes that this is not a qualified designer, because this is the designer's job.

If it is important, some people will say that there is no perfect thing in this world, don't worry, it's no big deal if you don't change it, don't bother!

When they ask the developer for help to fix this problem, the developer may say that it is a huge workload and takes a lot of time, and besides, it is just a pixel problem and has no big impact, so don't change it.

The product manager said: Our ultimate goal is to ensure rapid product iteration and ensure that the core functions are fine. No need to adjust 1 pixel, it's a waste of time~

Stop struggling, stop struggling, stop struggling!

At this time, a designer who is open-minded will probably give up such obsession. Although he is unwilling, he has no choice but to think: If I don’t want to change it, then don’t change it. Everything is imperfect.

As time goes by, the one-pixel problem increases. Eventually, when hundreds or even thousands of one-pixel problems accumulate, one day, users will ask, "Why is this software (webpage) so ugly? How did you design it? Are you incompetent?"

Everyone around the designer: “This is a problem with your design. Can’t you design well? There’s something wrong with your skills! There’s something wrong with your attitude!”

Designer: "..."

I think this is what happens to all of us. In the end, a messy software (webpage) is launched. As for the market response, you know...

I think the designer must have a thousand horses galloping in his mind at this moment.

A bad product is produced in countless compromises and one pixel misalignment. In today's situation where products are highly homogenized, users will naturally choose products with beautiful interfaces and easy to use.

If no one does the design, can the software be used?

Yes, it can be used. No one is doing design. The software can definitely be used, but it is very entangled to use. For example, when humans were still in ancient times, everyone ate raw meat, and no one thought it was wrong. Later, there was a SB (sorry to use such a word, sorry everyone) who loved to toss and turn said to everyone: "Well, in fact, meat roasted over fire tastes better." I guess many people said to him at that time: "What are you doing? Raw meat is delicious. Eating raw meat is enough. Eating roasted meat is too troublesome!" But in the end, cooked meat still defeated raw meat, and the result was that no one ate raw meat later. What static electricity wants to say is that it is not impossible to make do, but making do can no longer meet the increasingly high aesthetic needs of people today. People not only have to eat, but also have to eat enough, and then eat delicious food.

The same is true for the value of design. As for someone's remarks on ZhiX, programming is mandatory and design is optional. Static Electricity not only laughed, but also wanted to release a taunting skill: "In fact, programming is not optional, because eating is optional, living is optional, and everything else, go to hell! My dear, are you right?"

When designers start writing code and programmers start trying to design, what are you doing?

In fact, the problem of one pixel is not a problem at all. When the designer completes the design draft, the design is meticulous, and the markings are clear, the developer can follow the design draft and the degree of restoration is very high, basically reaching 80% to 90%. At this time, for some small details, Static Electric recommends that designers actively communicate and coordinate with developers to solve the problem. I believe that most developers are very willing to help us solve the problem. On the other hand, during the communication process, designers also need to understand how developers reproduce the design draft, how to write the code, how to make the layout reasonable, where problems can be avoided, and which ones can be solved together with developers.

During the APP development process, the computer is installed with the same operating environment as the developer (Xcode), and git is used to keep the code synchronized with the developer's code. This helps us understand the software production process. When necessary, we can also learn some tips on style adjustment. For designers, this will help them realize the design draft. For developers, they must welcome you to do this, because there is someone who can also write some code and help them solve problems instead of throwing them problems. So good friends were born.

During this process, a very good phenomenon is happening. As your relationship progresses, you, as a designer, can help the programmer very conveniently when he encounters color picking or some simple image problems. You can even help him install Photoshop and slowly teach him how to do some simple graphic processing.

In this way, mutual cooperation and harmonious communication are created. What are you doing at this time? Are you writing a sour article on ZhiX, or complaining about the other party endlessly?

Excellent designers and developers - communication and mutual understanding

In fact, we have been emphasizing communication. What is communication? Communication is the exchange between two parties. One-sided explanation while the other party is indifferent is not communication. We previously assumed that designers and developers are reasonable and their auras are not so contradictory. But what if they encounter a disagreement? Or the other party is just unwilling to change 1px? The reasons may be:

1. The design draft is not careful enough and is frequently changed. Designers, please imagine the situation when you make things for clients and make changes until you vomit blood.

2. If the design draft is careful and well marked, but the degree of restoration is always low, so low that you can't stand it. Then in addition to communication, there is also a problem of ability and attitude in front of you. If it is the first run-in, we can try to communicate. If both parties have a good attitude, the other party is generally willing to help; there is another situation, which is the most concerned issue, that is, the other party is extremely uncooperative. At this time, we need to ask the PM or your leader to act as a middleman to coordinate and successfully resolve the conflict. Remember, in this situation, the designer should not be too serious, otherwise it will be a tit-for-tat, and the result will be a lose-lose situation.

3. When the designer has achieved the consideration and understanding described in the second section, but the other party is still extremely uncooperative, which eventually leads to product problems, this is not something the designer can solve. I believe your superiors or leaders will have a deeper understanding and judgment of the whole situation. All you have to do is to do your job perfectly without any mistakes.

Because the quality of the final product is no longer something you can control, just let it go. Find your sense of accomplishment in other ways.

4. There is no perfect bug feedback and quality control mechanism, and problems are attributed to differences in individual cognition rather than process standardization.

5. Poor communication. I know you, the designer, are talking about making changes, but the developer may not care about you.

To our dear developers

1. We know that you are very busy, facing countless codes every day and countless bugs need to be fixed, but I really want to learn some code to share your pain.

2. We know that you are not a low-class code maniac with no taste. You must have a pursuit of perfection in your heart.

3. Please understand that communication is a two-way street. Oftentimes, we need you to tell designers who know nothing about code how to do better.

4. We know that simple, elegant and highly efficient code is your lifelong pursuit, but working with designers to modify a pixel problem might also be fun?

5. Our ultimate goal is the same, to make a satisfying product. Please trust the professionalism of the designer, even though you may be more talented than him.

6. The designer is happy to help you install some small tools on your computer to make it easier for you to develop interfaces.

7. Please stop saying hurtful things like: "A programmer needs to know Photoshop, so what's the point of having an artist?"

To myself - a designer working hard for 1 pixel

1. It is right to be strict with yourself. Please take every design and every 1px seriously.

2. If you have been abused by Party A’s perverted clients, please consider how you, as Party A, treat Party B now.

3. If a pixel can be adjusted once, don’t adjust it twice. If you adjust it repeatedly, it’s best to apologize to the developer and then learn how to adjust it yourself.

4. Learn simple codes. In fact, they are not that difficult and can even be fun. Try to ask engineers for help and ask them to install a development environment on your computer. I believe they will be happy to help you.

5. Our ultimate goal is the same, to make a satisfying product. Please trust the professionalism of the developer, even though you may be more talented than him.

6. Please believe that the distinction between professions will become increasingly blurred in the future. You are such a great designer who can write code, or perhaps a product manager who understands design, so let them envy you.

7. Try to believe that every developer is cute and kind. If you can't believe the above sentence, please don't give up looking.

Finally, I love every designer and development engineer who is dedicated to their work, motivated and has aspirations.