Shulou(Shulou.com)06/02 Report--

This article mainly introduces "what are the problems of the full-stack back-end development team". In the daily operation, I believe that many people have doubts about the problems of the full-stack back-end development team. The editor consulted all kinds of materials and sorted out the simple and useful operation methods. I hope it will be helpful for you to answer the questions of "what are the problems of the full-stack back-end development team?" Next, please follow the editor to study!

I. the role of the development team

In the group technical team, whether it is a full-stack back-end development team or a front-end separate development team, the development roles basically include back-end development, APP development and web front-end.

1. Responsibilities of each post of full-stack back-end development team

Web front-end, mainly responsible for writing static HTML, doing CSS well and some special effects JS

Back-end development, in addition to being responsible for the technical development of CRUD, but also putting HTML into template engines such as jsp and asp, needs to write JS code to do data rendering and most form verification, and even needs some HTML to call CSS (such as background management system, the front end is generally not allowed), it is necessary to write down interface documents for APP development.

APP development, brief

two。 The front and back ends separate the responsibilities of each position in the development team

Web front end, mainly responsible for static HTML,JS data rendering and form verification, including foreground system and background system

Back-end development, only responsible for CRUD technical development, write interface documents for web front-end development, APP development

APP development, brief

2. FAQs of full-stack back-end development team 1. Web front end is idle and has no technical content.

22 working days a month, on average, web front-end developers only have 10 working days of saturation per month, and spend the rest of their time blowing water, playing with their mobile phones, and considering job-hopping (because of disrelish panic, or have nothing to do, what they do is basically unskilled, want to find an environment with more room for development)

two。 CSS cannot unify the management of backend development suite pages.

When setting up a page, it often appears that after rendering the data, the effect of the page is not coordinated and the style needs to be optimized. Some people find it troublesome and think they can change it, so they write the inline style. There is no unified management of the front-end css.

3. JS cannot unify the management of backend development suite pages.

When doing form verification, the same code is often copied and pasted multiple times, and dozens of pages have 90% similar code. (if you are careful, you will usually draw public js references, but in fact, you still find it troublesome to copy and paste quickly.)

4. The back-end development is not good at writing pages, and the development efficiency is low.

When a back-end developer writes a page, it often occurs that it takes several hours or even a day to complete because of a JS effect, and some of the effects experience is poor, so it will be fine.

5. It is difficult for web front end to debug pages with data rendering locally.

Some problems will only occur after rendering according to the data returned by the backend. The web front end needs to be debugged, which is usually changed in the backend development seat, and the backend can only watch from the sidelines, wasting development effort.

Third, two kinds of team work flow 1. Full-stack back-end development team workflow

two。 Front and back end separate development team workflow

3. Analysis.

As can be seen from the figure, compared with the full-stack back-end development workflow, web front-end and back-end development increases the communication cost of interface docking, but generally speaking, it saves the responsibility of back-end development. Adjusting this time to the preparation of interface documents can promote the integrity of technical documents and strengthen team management.

Fourth, the comparison of the development staff of the two teams 1. The organizational structure of the full-stack back-end development team

2. Organizational structure of full-stack back-end development team

3. Require changes for every member of the team

Back-end development, front-end separation team mode increases the communication cost between web front-end and back-end development, but the actual scenario is similar to the docking of APP development and back-end development, so there is little difference.

Web front-end, in addition to the basic HTML, CSS, but also needs to know React, Vue.js and other JavaScript framework, higher technical requirements, but at present this kind of technology has become a necessary skill for web front-end interview.

The technical team leader, as a manager, although the role of the team has not changed much, because the web front end will also encounter problems, as a technical team leader, we must be able to provide some useful suggestions, so we should also strengthen the learning and understanding of some front-end knowledge.

At this point, the study on "what are the problems of the full-stack back-end development team" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.