preface
The writer is a former designer and now a front-end engineer. Today I want to talk about working with designers as front-end engineers (I really don’t feel like working this afternoon) in two main ways: 1. Communicate with respect and don’t call people “artists”. A good front-end engineer should know something about design (UX and UI).
A few tips
1. Fully understand the prototype/design draft
Good communication at work is based on mutual respect, especially for each other’s work. Prototypes are the end product of everything a designer does, and if you respect them as much as you respect your own code, then I believe you and the designer will become friends. In addition, understanding prototypes is good for an engineer’s career. Instead of writing code just to fulfill a requirement, think higher about why you’re doing it.
2. Communicate more beforehand
This point is particularly important, most engineers are introverted, many problems are not clearly expressed in the design draft, and engineers will be confused to do. When the designer sees that the work is already done, you either cut the code and start over, or force the designer to compromise. Either way, it will have an impact on your reputation and performance. It may also alarm your boss and make him think you are unreliable. It’s better if you keep showing the designer what you’re working on. That’s what the designer wants to see, and it’s also a chance for you to talk to each other and ask questions you’re not sure about. Besides, designers are mostly girls, so why not?
3, the final implementation details
Frequently changing designs is a pain in the ass, and we deal with these designers both by regulating them through the company’s workflow and by prioritizing UX implementation. We spent an hour drawing a beautiful button, only to see it look different the next day. In some cases, it’s not the designer’s intention to change, but the project may iterate quickly based on user feedback, in which case it’s just a matter of keeping a normal attitude. Consider yourself on the company’s payroll and put up with this little thing…
4. Don’t be afraid to offer your opinion
Sometimes the designer’s plan is not necessarily detailed in all aspects, this is the time for you to play, you can be unconstrained to achieve their ideas. Sometimes, the designer will spend a lot of time to implement the scheme proposed by the engineer. At this time, the engineer can put forward some alternative schemes based on the technology and explain the advantages and disadvantages to the designer. For example, if there is a particularly complex interaction in a requirement and the team has a tight schedule, you can actively communicate with the designer and ask him whether he can put the optimization of the experience into the next requirement and prioritize the functional requirements this time. The good thing about this is that if the experience need isn’t really important, he’ll probably forget the next one… In fact, many designers don’t necessarily have a better aesthetic than front-end engineers, but they just know how to design. The front end engineer is the person who actually implements the product and understands every detail more deeply. Plus having used a lot of good UI frameworks and being mature, front-end engineers have to believe in themselves.
5. Focus on design trends
Front-end engineers are not the creators of beauty, but they are the implementers of beauty. In this era of national focus on experience, beauty is already in demand. So front-end engineers need to improve their aesthetic. Here are a few good websites to recommend:
https://www.behance.net/; The world’s leading creative design aggregation platform https://dribbble.com/; Dynamic effect designer will be on the design of a super cool web site, https://www.pinterest.com/; A by the attention of the world, the world’s largest creative inspiration picture sharing website http://huaban.com/boards/28789790/; Domestic excellent photo sharing community at http://www.zcool.com.cn/u/13690550; Domestic comprehensive design website
Efforts to cultivate technology
It is the most effective way to improve skills and personal influence. If you’re already a leader and none of the above advice is for you, just say to the designer, “Don’t do that right now”…
conclusion
At the end of the article, I quote a well-known saying: most programmers and designers do not cooperate smoothly on the premise that both sides are too arrogant.