Should the front-end development position be subdivided into partial static and biased interaction

Yesterday morning on the micro-blog saw @ Front-End migrant workers sent a piece on the front-end work of the micro-blog, to the effect that the work of the front-end subdivision for the page refactoring (CSS) and JS Development limited the development of the engineer, and the page Function module development and maintenance will become fragmented, Limited to a certain extent JS and CSS to cooperate with the way, the company should not do so.

However, in fact, many internet companies are the front-end team, including our team, today to explore this issue, to see why many companies to the front-end work breakdown, what is the benefit of the front-end work breakdown, can solve those problems for us.

First of all, we clarify the responsibility of the front-end position, the input of the front-end position is ued department to the PSD effect map, the backend research and development to the API, output finished products. That is, to get ued department to the PSD effect map made of HTML, CSS, and then get the backend developed to the API, the completion of the foreground logic, front-end data interaction and other JavaScript development, the final output product and submit to the test.

From the front of the post responsibilities we can see that the front-end work can be divided into two kinds, one is biased static, that is, HTML, CSS development, one is biased interaction, that is, JavaScript, foreground logic and front-end interaction. These two kinds of work are very different to people's requirements, partial static can not involve too much programming and logic, but require cautious, can grasp the details, the visual experience is very sensitive to the user experience has a certain understanding, can endure IE6 and other browsers bring pain, can continue to learn, the latter for JavaScript requirements higher, Must have certain programming ability, familiar with the front and back end collaboration mode, familiar with HTML and CSS, have a certain front-end architecture capability.

From the point of view of the company formation team, it is difficult to find a class of excellent full stack front-end engineers. such as our Xinhui front-end team, now altogether 7 people, if we ask everyone to write HTML, CSS, JavaScript, foreground logic, front and rear interaction, and produce high-quality code that can be maintained, it's OK for many people, but do you know how hard it is to recruit so em? Now the market itself excellent front-end is very scarce, for a bat outside the internet company, perhaps 1 months can recruit less than 1 people you are satisfied with, however, if we change a way, find a few partial static, find a few biased interaction, relatively speaking, the difficulty is much smaller, Perhaps the original 4 months are difficult to recruit so em, now less than 2 months to do it. Do not underestimate this point, for many internet companies, speed is life, can not quickly build a good team and quickly put the product into the market, may mean that the end.

From the point of view of company employing cost, it can save a sum of money by dividing the front end into partial static and partial interaction. For each person is a high demand, natural costs are larger, however, if the personnel requirements are relatively lower, the cost will naturally come down.

In terms of team efficiency, it is efficient to subdivide the front-end into partial static and partial interactions. For example, the team has 50 pages to do, a total of 5 people, is everyone to do 10 static pages, and achieve all the JavaScript, foreground logic, front and back end interaction efficiency high? or 2 people to do all the static pages, 3 people complete JavaScript, foreground logic, front and back end interaction efficiency high? Definitely the latter, focus on doing static page students can do an average of 45 minutes of a page to complete, but if all do, it is difficult to do, and write JavaScript efficiency has become lower.

From the perspective of Team technology management, the front end is subdivided into partial static and partial interaction, the staff is relatively easy to manage, and it is easier to produce high-quality, maintainable code. The partial static several people can devote to the static this piece achieves the extreme, the partial interaction several people can commit to the interaction to achieve the ACME.

From the personal professional, the front-end subdivision for the partial static and partial interaction, reducing the front end of the employment threshold, with a certain skill is easier to settle down.

Some people say that the front-end segmentation so limited the JavaScript and CSS to cooperate with the way, to our team's practical experience of the group to tell you that JavaScript and CSS with no problem.

It is said that the front-end subdivision limits the engineer's professional ceiling. This in some cases is set up, but the personal professional ceiling is still more determined by the people themselves, a professional pursuit of the people will find ways to make their way more and more wide. Ma Yun used to be an English teacher, now is China's richest man, I was the Chinese teacher of the previous days is to dig coal workers, mainly by the people themselves decided. Of course if you want to do both static and interactive in your team, also very simple, it is said that Tencent some team can be round hillock, dry several months node.js, do a static page for several months, you put forward in your team, I believe you old General Assembly agreed, as long as the project is not very urgent.

We programmers want to be able to master more technology, proficient in the front and back of all the technology, beat Google, conquer the world, believe that our programmer's thinking is worthy of all people respect!

Finally a summary of it, (*^__^*), the front-end subdivision for the partial static and biased interaction, adapt to the development of the Internet business needs, is the inevitable trend of the future, no one can beat the trend!