A: Is it a wise choice to give up the back end to the front end?

A: Is it a wise choice to give up the back end to the front end?

2016.03.20 10:05:30

I was asked to answer a question: "Is it a wise choice to give up back-end to the front end?" 」 。

This problem, with the "front-end technical route and technical attitude of the dispute" seems to have recently known, Weibo discussion of hot spots, always represents a lot of thinking collision.

Today, while the weekend is a little idle, also to nag two, perhaps a registration open there is no way to live:

“

Well, I'm unconventional to first: laxatives ...

Remember the beginning with PHP, then the world of ASP, I did not like PO master so many ideas, I am still obsessed with PHP learning and practice. Later, the ASP is not, I have to rely on PHP to gain-I really did not have any foresight, entirely by fortune.

During this time, I found that Java is also very important, I began to see "core java", then "core java" is the first version. Gradually, with PHP to cope with fast-changing requirements, short-term development cycles and flexible projects, Java is responding to higher-demand projects.

Then, the front-end gradually engineering, modular/component, and do not know when, I mastered the front end.

From the present point of view, if a person is energetic, and a person to shoulder all the development tasks, self-feeling is not too much of a problem. But suppose that even if you have unlimited energy, is it really good for a person to take on the whole stack? Teams and organizations that can't afford to pay merely. "A project of one or two people, the more a person base project code, the greater the risk of the project"-This is my summary of the law.

Finally, I would like to say that the road is a person walking, but also need to plan, but you are not able to plan 100% clearly. This plan condensed into a sentence, that is: "As long as the idea is reasonable, it is set, and the idea as far as possible to do subtraction, do not fickle, the process of continuous improvement/adjustment."

We learn technology, the starting point is "came into being", not someone to give you framed "this semester is the study of Chinese, maths and English." However, the development of technology to today, engineering and scale characteristics is the norm, there must be a division of labor. In this case, each person's understanding of the technology or attitude is different, you are willing to focus on a certain area (such as PO Master General concept of the front end, the back end), there is no problem, one thing to focus on 100 years can be refined, on the contrary, constantly due to the situation needs what can be very good absorption, is also feasible. Measuring a person's value is not always about how much you know, but how much value you create. Why do we focus on technology now? That's because the technology base is really one of the prerequisites that might help you create value better. But always remind yourself: "To create greater value is the purpose." Figured out this point, what the front end, the back end will not become a lot of people's practice.

Finally, it is not necessary to compare PHP with JavaScript which is more developed and which is more money scene. Because Zuckerberg couldn't tell you, did he? The problem is slightly impetuous, the boss to see people, is to see you bring value, not to ask you to come and then with you to think "PHP and JavaScript which more development, which more money scene" ...

”

