What do front-end and back-end personnel look at full-stack engineers?

Baidu: full-stack engineer, also called full-End Engineer, FullStackdeveloper. It refers to people who have mastered multiple skills and can use multiple skills to complete products independently. I would like to ask if some of you who are currently engaged in front-end and back-end staff of web pages have some opinions on full-stack engineers, which will affect your work or better communication to facilitate the development of the entire website. Baidu: Full Stack engineer, also called Full-End Engineer, Full Stack developer. It refers to people who have mastered multiple skills and can use multiple skills to complete products independently.
I would like to ask if some of you who are currently engaged in front-end and back-end staff of web pages have some opinions on full-stack engineers, which will affect your work or better communication to facilitate the development of the entire website. Reply: I am mainly engaged in backend development and PHP and database adding when I enter the line. now I have front-end and back-end content in my work. I will give a rough talk about my views.

I think all programmers working on the web stack should become full-end engineers. it is very important to think about problems on the entire technology stack, sometimes even critical.

For example, when I used a function of a high-traffic website, I found it difficult to get a long-term scalability solution using PHP and the database within the company's hardware budget, this function requires multi-dimensional filtering of real-time data, and the frontend response should be controlled within 3 seconds. Generally, the website response should be less than 1 second, however, the availability of this function is delayed due to speed issues (the backend solution was used for more than 20 seconds and was basically unavailable ). Finally, we were inspired by some other similar websites to load data using ajax distributed parts on the front end, and then distribute the data to multiple web workers running in the browser, let them perform complex data computing, and then gradually pass the results to the main process render for users. this process does not involve blocking, and the single-chip data can be controlled below Ms, the user does not feel the need to wait. This is a core frontend-based solution that wins the pure backend solution.

Another example is from the front-end to the back-end. we have a relatively complicated mobile application. There are two groups of about 30 templates that need to be render, A considerable amount of data will use these 30 templates for render. Although the templates are all js pre-compiled, that is, there is no real-time parse problem, however, we still don't want to execute too many string concatenation (compiled js template) in mobile, and finally we integrate the data and template render into the backend, our rest api will directly generate a view that can be directly innerHTML. The frontend only needs to pass appropriate parameters to tell the backend how to render the view (full backend view ), this saves the front-end optimization we had to do. in this case, the optimization of the backend is much simpler.

As a result, full-end engineers do not understand one language, but are familiar with some technologies as easy as this. The difference between thinking at one end and thinking at the whole stack is true, it will profoundly affect your architecture and implementation. A lot of excellent development is stuck on the cut graph... I just want to work quietly on the front-end, but I think the backend level is really spicy. let's go.
I just want to work quietly on the front-end, but I think this UI level is really cool. come on.

The full stack development efficiency does not know where it is higher than them. I have been familiar with front-end database O & M, and I don't feel I have to label myself for a concept.

It used to be because small companies have no talent to do this. In the most difficult time, I worked with the artist, except the two bosses. no one was working. Later, I recruited two new people. after my graduation, I was very easy to teach! You took it seriously, and people thought you were low. then they ran away.

In fact, many full stacks were pushed out. later I found that this work was quite efficient, and then I continued to add the full stack label to myself.

If you don't want to do anything, the company won't be able to do it, and the salary won't be enough. if you don't want to use the full stack, you have to go to the full stack. Full-stack engineers are a wonderful vision, but there is a long way to go.
Currently, JavaScript has this potential. First, it solves the problem of inconsistent frontend and backend languages. it uses one language to solve problems in various scenarios.
(1) JS uses the browser's scripting language to implement frontend
(2) JS has some technical solutions and can even generate apps for Android and iOS.
(3) Node. js can be used as a Web Server
(4) Node. js can implement backend Server

JavaScript has done these things, but it is really difficult to be proficient in these four aspects at the same time.
The world is so big, such experts certainly have, but there should be no more.

Let professionals do professional things, and the division of labor will produce efficiency. If you only want to implement a function (or a small application), it will not be very difficult. However, if you want to implement a function, it is not easy to make it operate in various demanding scenarios (large-scale access, security, and good experience) with ease. In every aspect, there is a broad knowledge system behind it. the accumulation of technologies accumulated here is not easy to grasp in the short term.

Full stack may be one of the trends of future technologies. using one language/technology can solve all the problems. this is a kind of liberation for programmers themselves. However, there is a long way to go. Cut, we used to be in the webmaster community. that's what we have to do with design.
<(￣)> It is the most pleasant to work with the whole stack. Everything can be done to improve efficiency. It's not a skill point in the game that forces us to break into the real world. you can both learn and learn well, it depends on your personal abilities and efforts.
When you reach a certain level, the entire person's perspective will change a lot.
As for others' opinions, it is certainly not surprising that you should stick to what you think is right and continue to work hard. Now I am working on a single chip. it is already a single-chip web desktop...