The foreground of Web front-end development

There are always people like to talk about the front-end development has a promising no, a few days ago, a newly graduated college students asked me. Honestly I don't know how, but I like to do front-end development. To say that doing business is to challenge themselves, to do the front-end development is also very challenging their own, because the information update speed, to break the study, to study. Here is an article I came to the Internet, written very reasonable. Hope we do the front-end development of the heart can calm down, good learning. Because there is too much knowledge to learn. Here I say a word, clever, the line is a champion!

About a web front-end career planning, in fact, there are all kinds of answers, no answer is completely correct, all by their own choice, as long as they have chosen, adhere to seriously go, good. Here, I'm just briefly talking about my understanding of this piece of content. There is a point of view to share to everyone is: any planning and the realization of goals depend on the accumulation of knowledge, and the accumulation of knowledge from learning and learning a lot of practice. I provide a practical way, we can in the spare time on the Internet or outsourcing companies to take some private orders to do, because the goal is not to make money, we can use the lowest price to improve their competitiveness, access to a large number of orders means to obtain a large number of practical opportunities, but also some income as a result of work outside the Comfort award, It's still good.

I. Orientation of career orientation

First of all, only to determine their own career direction, to do a good job planning. In my opinion, the following are some of the career orientations that web front-end technologies can find:

(1) Senior Web front-end engineer

This direction is a Web front-end is the most basic choice, in foreign countries, many foreigners can make their own professional to achieve the ultimate, to a lifetime in a professional field of continuous learning and accumulation. Mainly lies in internal and external causes two aspects, the internal cause is the foreigner usually thought relatively simple direct, easy has been focused on one field, external cause is the foreign environment is very good, can support such career development road well. In the domestic, from the internal cause, the Web front-end technical staff is very impetuous, usually because the Web front-end knowledge of the update speed is too fast and feel that learning hard, and eventually turn to the backstage or other roads. From the external side, the Web front-end personnel did not receive a fair treatment, may be from the HTML page production began and inherited down, never the Web front-end staff is lower than the back, seemingly the front end is "superficial" synonymous, the back end is "abstruse" synonymous, This also directly creates the front-end staff's income can not be comparable with the back-end staff, while directly affecting the front-end talent market activity level. On the other hand, the front-end technology is easy to get started, creating another extreme situation: people flooding, talent scarcity. I want to all the Web front-end engineers said: Bread is always there, to withstand loneliness! I personally recommend this career direction, because, in this direction, as long as enough patience, thick and thin hair, the probability of success is very high. At the same time, this is the simplest way, we spend more on technical research, rather than office politics and other trivial matters.

(2) Senior Web architect

Say utilitarian, I like this direction, both the simplicity of the work, but also to reduce the actual coding of the workload can free more time to delve into technology. At home, web front-end engineers encounter more situations is always repeatedly writing the same code, always face the same technology and products, easy to feel boring. Because we have the widest range of web-related knowledge deposits, it makes it easier for us to become an architect. This career direction is not as smooth as the first one, mainly as an architect has to learn: back-end technology, DBA, platform and other content, and this kind of learning usually need to actually do the project, not to write two of the demo at home, it is bound to encounter a period of pain. Although not very smooth, but, for a bigger picture good, savvy, broad knowledge of the front-end engineers, I recommend you to take the strength, walk a glorious architect road.

(3) Start your own business

In fact, their own business is the best way, but also the lowest success rate of the road, challenges and opportunities coexist. Here, as a front-end technician, need to put their own vision more in the industry dynamics, industry chain dynamics, related product areas of the dynamic, the attention to detail of the advantages continue to maintain, at the same time, enhance their ability to control a product and even a company's destiny. However, the road and the technical path are slightly divided, and the follow-up will not be mentioned.

(4) Transfer management or other

Since this career path and web front-end technology is not much of a relationship, therefore, there is no discussion here, but whether or not to embark on this road, I feel that for any technical road, better bigger picture, a broader view of the good development of the necessary conditions, with good bigger picture and a broader perspective there is no other way, Can only continue to expand and accumulate knowledge horizontally, at the same time, more in the horizontal expansion of knowledge when the practice, the knowledge into skills.

II. Career Development Goals

I have a final goal, on this goal, we need to develop a series of learning and growth plans for ourselves, the following methods are developed:

First, to comb the knowledge structure;

The purpose of combing the knowledge structure is to understand clearly, what technologies are pre-built, which technologies are successors, which technologies are depth, which are breadth, and after combing the knowledge architecture in these two dimensions, we can accurately formulate clear growth goals and efficient growth plans.

Second, the decomposition of the target;

I think that can be divided into three stages, including: The initial stage, the stage of ascension, the molding phase. These three phases correspond to different objectives:

Initial stage:

1. Master of Basic knowledge

In the knowledge structure we comb, according to our analysis of the two dimensions of the most pre-and most obvious part, as the foundation of the stage, we must be more into the practice in this process, we usually do more and more skilled, we think this part of knowledge and content mastered.

2. Master of common tools

The mastery of common tools should be mastered by a number of popular tools with a large company or professional team background, the proficiency of these tools can enhance professionalism, professionalism, and can improve our efficiency. We only use Notepad to write pages, CSS, and scripts when we test ourselves for knowledge and skill proficiency.

3, the mastery of communication skills

Usually the person who does the technology will be positioned as "poor communication" of the person, this is why? The reason, mainly because more with the program and code to deal with, less communication with people caused. At this time, we should pay special attention to increase the opportunity to communicate with people, focusing on improving the ability of this child. On the other hand, we are often referred to as "people who do not understand communication skills." As a technician, myself included, there seems to be some inherent flaw in the difficulty of accepting challenges. At home, our technical staff are usually their own plans, their own implementation of the program, in the implementation process and lack of related products, interaction design and other personnel communication, mostly in their own ideas to carry out development, over time, we are accustomed to trust their own views, in their own perspective, for the challenges are always a variety of " Argued "strive. What we need more promotion is how to look at the problem from the perspective of the other side and how to look at the problem from the user's point of view.

4, good development habits

Development habits are developed, once there are bad habits, for the future to fix will be a lot of trouble, we cultivate good development habits must start from the beginning, for example: Before writing code, first write the document, write the comments first. The best way to define variables is to use directly understandable semantics, preferably pinyin, not English, especially unfamiliar words, in the future, I forgot to open powerword. Files preferably have a meaningful folder naming to manage, the file name is best meaningful, need the version number of the best can be updated with the project version number ... Wait a minute.

Ascension phase:

1. Mastery of advanced technology

In the promotion stage for knowledge and skills mastery, we need to comb the good knowledge structure to choose a deeper level of technology to learn, before we choose, we first by analogy or estimation method, to measure the difficulties of their own learning, to learn the difficulties and their least interested in the part of the main. This is the reason to recommend everyone: this stage of our interest is strong, has been through the bitter start stage, reached the stage of excitement, we have to use interest and excitement to challenge the most difficult part, in our confidence frustration and strong interest to find a balance. At the same time, supplemented by other deep-seated knowledge to study and study together.

2, product thinking of learning

Without the right product ideas, it is difficult to design a good program, no matter from the interface, interaction, or interface, logic, can not understand the product, understand the user needs, we will create a lot of trouble for ourselves, for example: We painstakingly use the latest technology, the most complex implementation of the function, but not to users or leaders, colleagues recognized. In order to make our work and study more efficient, to avoid useless, we need to constantly learn the idea of products, only understand the product ideas, we know with our technology to output what.

3, various framework of learning

Framework is our best means to improve work efficiency, for the framework of learning is the only way to grow. The course of our learning framework should usually be: use--"analysis--" personalization--"to imitate the writing of their own framework. Only a large number of use, to understand the design framework in the design behind the idea, only to understand the design of ideas, can do the right comprehensive analysis, only the right comprehensive analysis can support us to cut or expand it, only after the actual analysis, modification of other people's framework, it is possible to write excellent, their own framework. The usual course of study is: learning, understanding, imitation, creation.

4, rich client application of learning

With the increase in bandwidth and computer performance, as well as WEB2.0, rich-client applications flooded the Internet, and if you don't understand rich-client applications, you can't call it a qualified front-end technician. Can follow: Flash Animation-"flash programming-" flex--"-" air--"Silverlight Animation-" Silverlight programming steps to learn, first learn the cause of flash siverlight, A Silverlight is not too mature, and secondly, the actual Silverlight reference a lot of flash ideas, it is best to learn when not putting the cart before the horse.

5. Learning of various network protocols

Web front-end technology is the cloud technology, Cloud protocol has n, we should focus on learning: TCP/IP,UDP,HTTP,POP3,SMTP These protocols, in the development of Web front-end applications, these protocols are the carrier of our technology, and sometimes determine whether our application can achieve, Sometimes it determines whether our applications are high-performance, and these protocols are an important means of interacting with our backend technologies, which are like cipher dictionaries that help us interpret the ciphertext that is transmitted over the backend as plaintext that our front-end technology can understand.

6. Program Design

At this stage we need to learn oo, UML, design patterns, design methods ..., we want to make technology development work purposeful, planned, and these goals and plans must have theoretical support, so that we design the process can be more excellent, our development is more efficient, so that Our technology can be improved. Why should we study programming? Basically, even if we don't use Flash's ActionScript to write the program's front-end logic, we should at least plan our own JavaScript functions and package definitions to avoid problems in the future when we or others maintain the code. The program design ability, in the technical staff is still regarded as the programmer's this age, is the gray often, the ash often important drops.

Three, forming stage:

At this stage, I have nothing to say, if you can reach this stage, it proves that the follow-up growth path is colorful, is to become a senior Web front-end engineer, or become a senior Web architect, or other, have to specifically analyze their own characteristics and interests. If the senior front-end engineers, I think more important is to do new technology research, Internet technology development speed, constantly learning new technology, otherwise it will be eliminated. In addition, I suggest that in terms of breadth and depth of knowledge, it is best to pick one of the one or two areas that you are best at and most interested in in-depth study, not to pick too much, but not to be refined. If it's a veteran web architect's path, I recommend that you have a deep understanding of back-end technologies that must be accompanied by actual project development, based on the fact that several server--are designed and implemented by someone else's architecture.

The foreground of Web front-end development