A: Is it a wise choice to abandon the backend to the frontend?

A: Is it a wise choice to abandon the backend to the frontend? A: Is it a wise choice to abandon the backend to the frontend?

2016.03.20 10:05:30

Zhihu asked me to answer a question: "Is it a wise choice to give up switching the backend to the frontend ?」 .

This question is like a hot topic in recent discussions on the frontend technical route and technical attitude. it always represents a collision of many ideas.

Today, I am a little idle on weekends. I may be unable to handle the problem once I open it:

"

Well, I would also like to say: laxatives ......

I remember that when I started using PHP, it was still ASP. I didn't think as much as I did for the po master. I still insisted on PHP learning and practice. Later, ASP didn't work, but I had some gains from PHP. at that time, I had no foresight, but it was entirely Time-based.

During this period, I found that Java is also very important. I started to read "Core Java". at that time, "Core Java" was still the first version. Gradually, Java should deal with projects with rapid changes in demand and short and flexible development cycles.

In the future, the front-end will be gradually engineered, modularized/componentized, and I do not know when to master the front-end.

At present, if one is energetic and one is responsible for all the development tasks on the frontend and backend, it is not a big problem. But suppose that even if you have unlimited energy, is it really good to assume full stack work by one person? Those teams and organizations that cannot afford to pay for the cost will think so. "One project or two people work, the more project code a person base has, the greater the risk of this project."-this is my law.

Finally, I would like to say that the road is made by people and needs to be planned, but you cannot make it clear in 100%. This plan is integrated into one sentence: "As long as it is a reasonable idea, it should be settled. at the same time, the idea should be reduced as much as possible. do not go into the dark and the process should be constantly improved/adjusted ".

The starting point for us to learn technology is "coming into being". no one will give you the question "What we are learning is Chinese, mathematics, and English this semester ". However, with the development of technology, engineering and scale are the norm and division of labor is inevitable. In this case, everyone's understanding or attitude towards technology varies from person to person. you are willing to focus on a certain field (such as front-end and back-end of the general concept of the po Master, one thing that focuses on 100 can also be refined. On the contrary, it is also feasible to constantly absorb what is needed in response to the current situation. Measuring the Value of a person is often not about how powerful your technology is, but about how much value you create. Why do we focus on technology now? That is because the technical foundation is indeed one of the prerequisites that may help you create value better. But always remind yourself: "creating greater value is the purpose ". After thinking about this, the frontend and backend will not become the obsession of many people.

At last, it is unnecessary to compare PHP and JavaScript with which one is more advanced and which is more profitable. Because Zuckerberg cannot tell you either, right? This problem is a little impetuous. the boss looks at people and the value you bring, rather than asking you to come and think with you about "which PHP and JavaScript are more advanced and which is more profitable ......

"