Veteran summarizes 10 learning styles that hinder progress

1. Preface

Engaged in the Web front-end of many people, everyone's learning style, learning habits are basically not the same! About the Web front end (or direct Internet), we all know, is to do old, learn an old industry. Before writing the article, I said a lot of learning ways and suggestions. Today change, say I personally do not suggest the way of learning, or I personally think is hinder the progress of learning, I hope everyone lesson! If you have anything to add and advise, please point out. We exchange views together, help each other!

2. Specific circumstances

1. Just watch the tutorial, do not do hands-on combat

This can be said to be the biggest taboo to learn, but also reminds the most of a note is a matter! Online tutorials have many, various languages, various knowledge points, all aspects of the JAVASCRIPT,HTML5,CSS3, and so on some, any search on a lot, after all, one of the biggest advantage of the Internet is the sharing of resources! But a lot of people look at the tutorial just to see the tutorial, not hands-on exercise. Even if the blog of the tutorial, video tutorial again good, do not do hands-on, write code, this way of learning, memory is not deep, easy to forget, in the end, may have learned nothing! And some tutorials, if not followed by hands-on exercises, may be blindfolded. Personal advice: To pick the one that feels right for you, do it yourself and write the code. Even if you are not watching tutorial writing code! After reading the tutorial, be sure to do your own hands-on exercise! Process, you may encounter some problems, but this will learn more, memory is more solid!

2. Learn only frames or libraries

In this case, for JavaScript (hereinafter referred to as JS) is not serious now, during my college and internship, that time is still the times of jquery. Many people will say when chatting: with jquery, why do you want to learn JS? With Vue, why do you learn JS? In the face of such questions, I did not answer at that time, I think: jquery or Vue is to use JS to achieve, do not JS, learn jquery or Vue first study, the second study jquery or Vue certainly not very deep. And, in case the project is not allowed to use jquery or Vue at times, it's basically not going to write code. At this time, if you learn other frameworks or libraries, basically it is equivalent to re-learn a language. Personal advice: first put the foundation (HTML+CSS+JS) firmly, and then learn other frameworks or libraries. Although in the case of JS, I dare not say that learning JS framework or library is to check the document, check the API. But at least learning JS frame or library can not be so difficult!

3. Write the Code

This is my previous habit, only to write code, do not know: coupling, instantiation, inheritance and other professional terminology, and other people to communicate, infinite circle! I don't even know what people are talking about! The technical update of the Internet is very fast, and go out releases a framework, a library, and a tool. Although not every newer technology requires learning. But if you only write code, don't know the new technology. It's easy to make yourself stop and lose your competitive edge. Personal advice: In addition to writing code, to ensure that you do not understand the code, there is no understanding of the code. and pay more attention to the news, see if there are any technical updates! If you feel that the updated technology is very practical, or if you are interested, you can learn more! After all, the Internet is an old, learned an old field, technology updates quickly, if not keep up with the trend of fashion, maybe they will be eliminated!

4. Access to complex projects too early

This situation is more prevalent, both in schools and now in training institutions. Many study front-end people, the foundation did not fight, there is a threat to do a big project, I heard some people want to do know, some people want to do the century good edge and so some great goals! But all the people are even the Web site business process and logic are not clear, finally the more disorderly, give up! Before the great goal has become a rotten tail building, the role of the most is a code exercise! It took a lot of time to do something that didn't make much sense! Personal advice: From simple to complex, complex sites, there are a lot of simple modules. You may wish to start with a simple function, finish a function and then add the function inside! Now the company is the case, the development of the back-end management system, developed a few months, from a only employee login registration function, and then add the function, to now the project gradually improve! (Web front-end Learning Exchange Group: 328058344 prohibit small talk, non-happy do not enter!) ）

5. Ambitious and anxious

This situation is more common in the training institutions out of the people. I don't know if all the cities are like this, but here in Guangzhou, I feel like this. Is the goal is unrealistic, to oneself also not enough to know! Before the group chat, in gold three silver four that period of time, many people looking for work, chatting when also met many training institutions of people. Resume is a variety of proficiency, just graduated in training institutions for a few months, or to bring two or three years of work experience, or to say that they have been training for several months, the technical level and the market for two or three years of people almost. The whole thing is to blow yourself to the almighty! But a question, ten ask nine don't know. Ask what the closure is, don't know, ask what the prototype is, don't know. Ask what inheritance is, or do not know. Here's the next question I've been impressed with. I'm the one who's dealing with this problem! See who is proficient in all kinds of blows. I immediately out of this problem, no one can answer correctly, the title is below!

Alert (a) a (); var a=3;function a () {alert (+)} alert (a) a=6;a ();

Above said, is only a superficial phenomenon, more importantly, the situation is too ambitious, it is likely to lead to their own hard to find a job! Because some companies think the highest can only give you 4000 salary, but you think you have the strength to get more than 9000 of the salary. It's hard to find a job in this situation! The impression is not good! More importantly, this may affect your career choices! Personal advice: Evaluate yourself from a practical standpoint. Think of what they will, what can bring to the enterprise! Can also stop other people's advice, and compare the technical level and wages of others, or the internet to find some interview questions, see if they can complete those face test! Finally evaluate oneself, think oneself is in what position!

6. See the difficulty to escape

This, believe that a lot of people have feelings, on the development, encountered the last or several of their own feel no way to achieve the needs or functions. Try to escape, for example: This function is not very important, do not do it? I've never had this function, I can't make it. This function is outsourced to others to do it, we can not do it! A lot of escape words. We can think of, if every time is to escape, then the time, their technical level is still stuck in the foundation that stage? How to improve their technical level in the future. Personal advice: Meet the difficulties. In the Web front-end development of this piece, if encountering a problem is normal, if you have not encountered a problem is to see ghosts! Facing the problem, we should challenge the problem, not escape! Everyone wants to improve their technical level, challenge the problem is not a good skill to improve the actual combat opportunities? If you finish the problem that you thought was impossible to complete, this is a witness of the technical improvement! Isn't it? I also feel that every day to write simple business code, do not explore new knowledge, do not challenge the problem, so do not develop a lot of meaning!

7. You can use the line, do not want to optimize

This is also a very common situation, many people think that the code can be used to write the line, to achieve the needs of the line! No matter the future optimization. In the development of the project or the development of plug-ins, although I also advocate: first realize, and then optimize this way! But does not mean that I finished the development is over, no longer want to optimize! If you do not try to optimize your code, do not explore the better way to write code, not to write high-quality, concise code, because they have to learn to write high-quality, concise code of an important way to the blockade. Another is that, on the project, some of the problems may be potential, that is, now look at the project is not a problem, but it does not mean that future problems will not occur. Instead, after the project has been developed, try to optimize your code, explore better ways to implement it, and try to write high-quality, concise code. Isn't it a good learning process? There are a lot of ways to optimize the code, like often: is the code too repetitive and does it introduce design patterns? Website Performance general, can be optimized? ), optimize this piece, not to say one step to optimize to the best, but at least not worse than before! On optimization, I have also sent some resources before. Very easy to find, online resources are many! You can pick and choose!

8. Do not know and do not understand the question immediately

Do not know not to ask, this everyone knows, is encountered problems, never ask colleagues or through other ways to consult others. is to try to solve the various solutions. In this way, the worst-case scenario is that eventually the problem is not solved and the colleague asks for the development. The best results solve the problem, but it takes a lot of time to solve the problem. Do not understand immediately ask, this is the meaning of the word surface. Ask someone immediately if you have a problem. I don't think very much or think at all. This solves the problem, but it can lead to frequent questioning of colleagues and the impatience of colleagues. If the patience of the colleague is worn out, the tone of the answer may not be very good. This will not only affect the relationship between colleagues, but also to be afraid to ask colleagues, have to let themselves in the above said do not understand the risk of not asking. Personal advice: timely advice. Encounter not understand the problem, the first of their own context thinking, think of whether you have encountered this problem before, can not solve the network to find solutions, if not solve the problem, this time to ask others, ask colleagues or through other channels to ask others. So I have a thinking, solve the problem when the memory is also very deep, do not disturb colleagues frequently!

9. Pretend

This time is similar to the above, but it is not the same! Pretend is to ask others, in fact, the explanation of others did not fully understand, may be due to face or because embarrassed to disturb others so long, or worry about disturbing others too long, so pretend to understand. But this may be a moment of flicker, and soon will be revealed. This will make the other person to ask the same questions, so it will make others more embarrassing, more embarrassing! I will disturb others more time! Personal advice: If you have a question to ask someone, just ask someone who is not a very impatient person. He will answer your questions patiently! Therefore, when asked other people's questions, it is important to ensure that they have already understood the cause of the problem, colleagues did not explain clearly, their direct answer does not understand, I believe many people will explain in detail again. If you are worried about a colleague's busy work or other reasons, you can choose a suitable time! I now ask colleagues is, or do not ask, to ask on the bottom to understand! Of course, my colleagues are very patient, every time I have any problems, they will be patient to answer, or even expand to open the speaking!

10. Write the code without understanding the requirements

A lot of people get the demand, the first reaction is to write code, even if they do not have to clarify the needs of the same code before writing. Another situation is that many people are writing code while they want to. This way of development, in case you understand the needs of the wrong! May result in the code you write, a large part of it to be modified, or even delete all overrides. Do not understand the need to write code this situation, the probability of occurrence should be quite large, but in general it is difficult to find this situation, after all, the programmer to the code of the additions and deletions is normal! I do not know, is in a technology sharing, the eldest brother proposed, his proposal is for some slightly more complex needs, the first clear requirements, simple draw a flowchart, and then in the code, first write a note, and then start to write code! For this, I am now in the midst of execution! Unless the demand is really simple, I will simply draw a flowchart on the draft. According to the flowchart, write good comments, and then write code, this will be more organized, the code is clear, the future rework may have, but not as much as before! In the development time, efficiency, has been a promotion!

3. Summary

Web front-end now the market, I do not know other cities, but Guangzhou is really not good, the competition is also very large, almost 100 people for a position, the reason is that the training institutions and the front-end easy to get started. In the face of this situation, we can do, only time to learn, improve their technical level. This will ensure that they are very competitive and can stand out from so many people. For learning and promoting themselves, in addition to the appropriate way of learning, but also to some hinder the progress of learning ways lesson! The above 10 points are some of my own ideas. Hope to be useful to everyone! The last one is, if there is any good learning style or bad learning style, welcome to the guidance. Let everyone exchange views, learn from each other!