The development team always feel that the front-end engineer's cooperation is not enough, the use rate is not high, there is a good word, the development process of grinding is to see where there are short board will be a way to improve the short board.
The role of the front-end members of the function are inconsistent, roughly divided into the following 2 categories:
Type 1, design the UI page, and implement the final page with static HTML, such that the front-end, more inclined to the UI. It's the equivalent of grabbing some of the front-end work from the UI designer.
Type 2, according to the design of the UI designer, design a static page, and add some interactive effects, such as input content verification, the other end, and back-end engineers to complete the simple commit interaction;
Here I would like to say is the second type of front-end, they are more inclined to program development, have logical thinking ability, skills, understand css,html,js, need to understand jquery,extjs,bootstrap and other JS and CSS framework; Project practice will find that the use of such jobs is not high. Because, do not participate in product design, do not consider the business implementation: As long as the UI out of the picture, the static page implementation is OK, the following is waiting for the back end set diagram. A lot of late new requirements, no changes to the page, the front-end also need less input, timely investment, design specifications have been formed, there is no much work. You will find that front-end engineers do not have the business logic to understand the relationship.
This is how I see the arrangement of the job:
Mode 1: Do not use a dedicated front-end engineer;
--for the page to C can be fully outsourced to the company to do, or in the early stages of the project to find an existing product to imitate, and then recruit their own front-end engineers;
-For the to B or Administrator page, you can use the open-source framework such as Bootstrap to write, is more than enough;
Mode 2: Find a UI designer who can write Web pages;
--the equivalent part of the front-end assigned to the UI designer, part assigned to the backend engineer;
Mode 3: Add a lot of work to the front end
--Static page set diagram is done by the front end: This may not be easy to understand, let the front-end to write PHP or Java EE; This is not true: You can imagine the client and server side of the match, the client is responsible for the page rendering and a small amount of amateur logic judgment, the server side provides interface. Web front-end and back-end can also be used in such a way, the front end through Ajax to obtain data, and then the page assembly;
--In addition to the business page, in fact, there are many promotional page design, can be synchronized to start;
--the implementation of the front-end architecture: equivalent to having its own set of design specifications, so that the backend can also participate in the page design, if there is insufficient manpower.
Feelings:
It is estimated that some children's boots will sour to say that this is going to save the manpower; indeed, how a project will take into account cost and efficiency issues from the start-up, how to set up a team and excavate team efficiency is the responsibility of the manager. In addition, you can imagine that if a team of all people are busy, but there is a person can not contribute to the project: He will be what kind of feeling, powerful make not? What other people will feel, why I work overtime every day, and he is very quiet? The boss will think, give your people not to make full use of, this manager must have a problem?
The architecture of technology is designed not only to adapt to products and businesses, but also sometimes because of organizational features.
Mining the residual value of Web front-end engineers
