The so-called technical industry has a specialization, and it is normal for designers to not understand development, but whether the design draft can be implemented ultimately depends on whether the programmer can realize it. At this time, the problem comes. Some designers are very creative, but when the programmer says that it is impossible to achieve in front of the programmer, they are almost ashes, and their hearts are galloping: I can't do it, **. At this moment, the programmer's psychology: I don't even know this common sense, and I don't want to talk anymore.
Why does everyone feel like playing the piano to a cow? Most designers are art students and right-brain thinkers, and they are good at studying and working in spatial imagination, art, etc.; programmers are basically science students and left-brain thinkers, and they are good at learning and working in logical reasoning and other aspects. , so it can be considered that the two ways of thinking are not the same.
It is estimated that most designers will firmly believe when they hear "this development cost is very high" and "this is impossible to achieve". Even if they doubt, they don't know how to prove that the cost is not very large or can be realized, and then they go to find a downgrade plan. There is even a big gap between the final solution and the best solution.
First of all, we have to say one thing very objectively. The programmer's favorite sentence "As long as you give a plan, I can implement it for you" is basically correct, because as long as there is enough time to think about it and implementation, there is no solution. Then why did you reject your plan with "this development cost is very high" and "this is impossible to achieve"? In the end, it is a matter of time, but the decision time is ultimately determined by the difficulty of the program and the ability of the programmer such as IQ, experience, programming ability and manpower. The abstract summary is an inverse proportional function Y=Z/X (Z is a constant).
Due to limited time, programmers don't want to waste time on some work that has no value to themselves, such as adjusting visual details. Let me briefly introduce what programmers want to do and don't want to do:
Talk about a little bit of animation. Dynamic effect implementation has always been a shortcoming of most programmers in China. First of all, most computer majors do not have courses dedicated to teaching front-end or client-side development, let alone dynamic effect implementation teaching; coupled with the lack of online resources and strong dependence on dynamic effect implementation Design (can't do it alone), so it is quite difficult for programmers to learn motion development. A good dynamic effect needs to be adjusted slowly, which is very time-consuming, so most programmers don't like to waste time on dynamic effect implementation. #Forcing a person to do b2b data something short board is estimated that no one is willing, the designer should understand#
In the project process, the design belongs to the upstream of the development, so the designer is obliged to check the design draft before handing it over to the development. As a designer with a development background, let me tell you how programmers think about your design draft, and then introduce a relatively simple development cost assessment method to help you evaluate your own design draft, so that your The possibility of the design draft landing will be higher.
Let’s start by comparing how designers and programmers view the entire product: