How to systematically get started with web front-end for beginners? Here's a piece of advice from someone who's been here

How to systematically get started with Web front-end for beginners? Here is a piece of advice from someone who has come here, let's take a look with the editor of Qianfeng Guangzhou!

First, sort out the knowledge structure;

The purpose of sorting out the knowledge structure is to understand clearly which technologies are the predecessors, which technologies are the successors, which technologies are the depth, and which technologies are the breadth. After sorting out the knowledge structure according to these two dimensions, we can accurately formulate clear growth goals and efficient growth plans.

Second, decompose the target;

In my opinion, it can be roughly decomposed into three stages, including: the initial stage, the upgrading stage, and the forming stage. These three stages correspond to different goals:

Initial stage:

1. Mastery of basic knowledge

In the knowledge structure we have sorted out, according to the most advanced and simple part of the two dimensions we analyzed, as the stage of laying the foundation, we must invest more in practice in this process. We usually do More and more proficient, it is considered that this part of the knowledge and content has been mastered.

2. Mastery of common tools

For the mastery of common tools, you should master some popular tools with the background of large companies or professional teams. The mastery of these tools can improve professionalism and professionalism, and at the same time, can improve our work efficiency. Only when we test our proficiency in knowledge and skills will we use Notepad to write pages, CSS, and scripts.

3. Mastering communication skills

Usually people who do technology will be positioned as "poor communication" people, why is this? The reason is mainly because they deal more with programs and codes, and have less communication with people. At this time, we should pay special attention to increasing the opportunity to communicate with people and focus on improving the ability in this area.

On the other hand, we are often referred to as "no communication skills" people. As a techie, myself included, it seems to be inherently difficult to accept challenges. In China, our technicians usually formulate and implement their own plans. During the implementation process, there is a lack of communication between related products and interaction design personnel. Most of them develop under their own ideas. Over time, we are used to Trust your own point of view to look at problems from your own perspective, and always strive to "justify" the challenges in every possible way. What we need to improve more is how to look at problems from the perspective of the other party and how to look at problems from the perspective of users.

4. Good development habits

Development habits are formed. Once there are bad habits, it will be a lot of trouble to correct them in the future. When we cultivate good development habits, we must start from the beginning, for example: before writing code, analyze, Documentation, write comments first. It is best to define variables with directly understandable semantics, preferably Pinyin. Don't use English, especially uncommon words. In the future, you will forget to open Kingsoft PowerWord. The files are best managed with meaningful folder names, the file names are preferably meaningful, and the version number that needs to be the same as the project version number - the same...etc.

Ascension stage:

1. Mastery of advanced technology

For the mastery of knowledge and skills in the upgrading stage, we need to choose a deeper level of technology from the sorted knowledge structure to learn. Before choosing, we first measure the difficulty of our own learning by analogy or estimation method, so as to learn the difficulty and Focus on the parts you are least interested in. The reason for recommending this is: at this stage, we are very interested, we have passed the bitter initial stage, and reached the exciting stage of promotion. We need to use our interest and excitement to challenge the most difficult part.

We find a balance between frustrated confidence and intense interest. At the same time, supplemented by other in-depth knowledge to study and research together.

2. Learning about product ideas

Without the correct product ideas, it is difficult to design a good program. Whether it is from the interface, interaction, or interface and logic, if we cannot understand the product and user needs, we will cause ourselves a lot of trouble. The functions made with the latest technology and the most complex implementation are not recognized by users, leaders and colleagues. In order to make our work and study more efficient and avoid useless work, we need to constantly learn the idea of ​​​​the product. Only when we understand the idea of ​​​​the product, can we know what to output with our technology.

3. Learning about various frameworks

The framework is an excellent means for us to improve work efficiency, and the learning of the framework is the only way to grow. The route we take to learn the framework should usually be: use -> analysis -> personalization -> imitate and write your own framework. Only after a lot of use can we understand the thinking behind the design of the framers. Only when we understand the thinking of the design can we make a correct and comprehensive analysis. Only a correct and comprehensive analysis can support us to cut or expand it. Only after actual analysis, Only by modifying other people's frameworks is it possible to write excellent and own frameworks. The usual route of learning is: learn, understand, imitate, create.

4. Learning of rich client applications

With the improvement of bandwidth and computer performance, and WEB2.0 in full swing, rich client applications are flooding the Internet. If you don't know rich client applications, you can't be called a qualified front-end technician. You can follow: Flash animation->Flash programming->Flex->->Air->Silverlight animation->Silverlight programming steps to learn, first learn Flash and then learn Silverlight because Silverlight is not yet mature, second, the actual Silverlight Drawing on a lot of Flash's ideas, it is best not to turn it upside down when learning.

5. Learning of various network protocols

WEB front-end technology is the technology on the cloud. There are N kinds of cloud protocols. We should focus on learning: TCP/IP, UDP, HTTP, POP3, SMTP these protocols. In the process of developing WEB front-end applications, these protocols are our The carrier of technology sometimes determines whether our application can be implemented, and sometimes determines whether our application is high-performance. At the same time, these protocols are also an important means for us to interact with back-end technologies. These protocols are like password dictionaries, helping We interpret the ciphertext transmitted by the backend into plaintext that our front-end technology can understand.

6. Programming

At this stage, we need to learn 00, UML, design patterns, design methods... We want to make technical development work purposeful and planned, and these purposes and plans must be supported by theory, so that , The programs we design can be better, our development can be more efficient, so that our technology can be improved. Why learn programming? Mainly, even if we don't use Flash's ActionScript to write the front-end logic of the program, we should at least plan the definition of our own Javascript functions and packages to avoid problems when we or others maintain the code in the future. Programming ability, in this era when technicians are still regarded as programmers, is very, very important.

The above is the content shared today, I hope to help you!