Design thinking: About front-end design and other job coordination

Finally have time meditation thought for a moment W3ctech exchange topic, feel or write a little good, before Yupo classmate send to the topic, always think this is a too general topic, but then think again, this is indeed a topic worth discussing: How does the front-end engineer work together with other positions?

First of all, this topic should be cut from three levels of high school, because of the so-called collaborative work in different companies in different environments, and even different departments are differences, not to say that the company or departments have to be divided into three levels to discuss, but I think there is really a big difference between them.

Low-level collaboration I think in small teams more, its role division is very simple customer (OR boss), design, front-end, background development, in this assembly line, the front-end needs to contact with the three parties, need to understand the customer to mention the interactive needs of the page, need to know the design intention of the designer, need to consider the implementation of background development interface, This is a more traditional way of collaborating, or some people call linear collaboration, and in fact that is the old pipelining, the front is still not efficient work, the specific performance of communication with customers is not smooth, front-end engineers cut into the professional code-level points, and customers tend to focus on the ultimate effect, Separation or disconnection from the designer, such as front-end complaining about the ignorance of the design of the browser, or the design complained that the front end can not be perfect to restore their work, and do not understand the background architecture ignores the dynamic situation of the page implementation, or background development directly involved in the foreground code, and so on. In this mode of collaboration, the front-end is a weak professional role, and because of this, many small companies basically ignore this position, even the design and the front-end one to play, I think in this mode, the promotion of collaboration efficiency depends entirely on the personal ability of the front-end, such as you can use in-depth words to communicate with customers , you can when the designer complained to explain to him why can not be achieved, you can set aside the implementation of dynamic code demo, and so on, or even you can talk about the design of a wide range of designers can talk with the background development of the background structure, but in short, I think the efficiency of this model is difficult

Intermediate collaboration, the corresponding model of the role division more detailed, such as Product Manager intervention, there are interactive design and UE participation, and so on, the most critical is the front-end to participate in the project process, he from the initial project to follow, from a professional point of view to cooperate with each position to do this thing. Many of the professional web team will be configured to do so, in this mode, the front-end needs more strong professional influence, from the beginning of the project there is a clearer road map, in the follow-up process with each aspect of the involved people to deal with, to promote this matter to complete the perfect thing to join the link, To discuss the ideal product architecture with the product manager, discuss with the designer the details of the design and the implementation of interaction, and background development to discuss code-level optimization, in this mode, the efficiency of the promotion should come from a more complete participation mechanism, such as the front-end in what node intervention, depth of intervention, etc. I think the front-end in the beginning will be involved in the project, but not necessarily very in-depth, so you can fully understand the background of the project, the early stage should be with the relevant positions of personnel together to develop an outline, when the side straighten out can enter the design link, in the design process with the design of the details In front of the output page should be with background development on the interface to make an early access, such as a given interface mode, and finally the output page, of course, this is not finished, there are test evaluation and continuous version of the iteration.

Intermediate collaboration may seem perfect, but there are some regrets, such collaboration is still a need for front-end engineers strong personal ability, can not be modeled, I think more advanced collaboration is to introduce the role of the front-end architect, about the function of the front-end architect, I think in short, he is a dedicated to do these collaborative work, The following is a reference to the Kejun's career description for the front-end architect:

1. He needs to develop a technical programme that is more efficient in conjunction with the upstream and downstream links. Specifically, improve the template (view layer) development, team internal development, maintenance and testing methods.

2. He wants to check the implementation of various technologies. What kind of good, what kind of risk, which is not mature, which cost is high. Need to "grasp the crux of the problem, balance design" ability.

3. He will take the initiative to jointly related departments, from the performance, ease of use, security and other aspects to enhance product value and competitiveness.

4. He wants to correctly select the appropriate framework and library (or design such a framework and library) for the product and establish a complete normative system. Ensure the consistency of the Code style (solve the problem of development efficiency).

5. He wants to be forward-looking. The introduction of advanced front-end technology landed in the specific products.

6. He is responsible for the selection of team members.

7. He's going to be able to do PowerPoint and preach to the top.

Said more specific, if a team has such a role, then the collaboration with other positions will be unified and stereotyped, front-end engineers in the framework of the architect can better play their professional skills, of course, this is the ideal state, I think in the current situation, In the team can cultivate some of the front-end engineer's architectural ideas, and try to develop a number of collaborative frameworks, a good system is always better than the individual strong, only the establishment of efficient collaboration mechanism to ensure that in a variety of different teams to collaborate efficiently.