Veterans summarize 10 learning methods that hinder progress

1. Preface

There are many people engaged in web front-end, and everyone’s learning methods and learning habits are basically not exactly the same! As for the web front-end (or directly the Internet), everyone knows that it is an industry where you get old and learn. When I wrote an article before, I mentioned many learning methods and suggestions. Let’s change today and talk about the learning methods that I personally don’t recommend, or the learning methods that I personally think hinder progress. I hope everyone can learn from them! If you have anything to add or point out, please point it out. Let’s exchange opinions and help each other!

2. Specific situation

1. Just watch the tutorials and not practice it

This can be said to be the biggest taboo in learning, and it is also the one I have been reminded of the most. matter! There are many tutorials on the Internet, covering various languages, various knowledge points, and various aspects, such as javascript, html5, css3, etc. You can find a lot of them just by searching. After all, one of the biggest advantages of the Internet is resource sharing! But many people just read the tutorials and don't do the actual operation. No matter how good the tutorials on the blog or the video tutorials are, if you don’t do it yourself and write code, this way of learning will not be deeply remembered and easy to forget. In the end, you may not have learned anything! And there are some tutorials, if you don't follow the hands-on practice, you may get confused. Personal advice: Choose a tutorial that suits you, and also practice it and write code. Even if you’re not writing code while watching tutorials! After reading the tutorial, be sure to practice it yourself! You may encounter some problems during the process, but in this way you will learn more and your memory will be stronger!

2. Only learn frameworks or libraries

This situation is not as serious as before for javascript (hereinafter referred to as: js). During my university and internship, jquery was still the leader at that time. when. Many people will say when chatting: Why do we need to learn js when we have jquery? With vue, why do you need to learn js? Faced with such a question, I didn't answer at that time. I thought to myself: jquery or vue is implemented using js. If you don't know js, learning jquery or vue will be difficult at first, and it will definitely not be very in-depth when learning jquery or vue. Moreover, if sometimes the project does not allow the use of jquery or vue, then you will basically not be able to write code. At this time, if you learn other frameworks or libraries, it is basically equivalent to learning a new language. Personal suggestion: lay a solid foundation (html+css+js) first, and then learn other frameworks or libraries. Although I know JS, I dare not say that learning JS framework or library is just to check the documentation and API. But at least learning js framework or library will not be so difficult!

3. Just focus on writing code

This is a habit I had before. I only focus on writing code. I don’t know: coupling, instantiation, inheritance and other professional terms. When communicating with others, I am endlessly confused. lock up! Have no idea what others are talking about! The technology of the Internet is updated very quickly. A framework, a library, and a tool are released every now and then. Although not every newer technology requires learning. But if you just focus on writing code and don’t understand new technologies. This can easily make you stop moving forward and lose your competitiveness. Personal suggestion: While writing code, make sure that you understand the code and have an understanding of the code. And pay more attention to the news to see if there are any technical updates! If you think the newer technology is useful or you are interested, you can learn more about it! After all, the Internet is a field where you have to learn as you learn. Technology updates very quickly. If you can't keep up with the popular trends, you might be eliminated!

4. Contact with complex projects too early

This situation is relatively common, whether in schools or current training institutions. Many people who are learning front-end have not laid a solid foundation, so they threaten to do a big project. I heard that some people want to do Zhihu, and some people want to achieve great goals such as the Good Fortune of the Century and so on! But none of them even understood the business processes and logic of the website. In the end, it became more and more confusing and they gave up! The great goals before have become unfinished projects, and the most useful function is just a code exercise! I spent a lot of time doing something that has no practical significance! Personal suggestion: From simple to complex, complex websites have many simple modules. You might as well start with simple functions first, and then add functions to it after completing one function! This is the case for the company I am currently working in. The backend management system has been developed for several months. From a function that only had employees’ login and registration, to adding functions one by one, the project is now gradually improving! (Web front-end learning exchange group: 328058344 No chatting, please don’t enter unless you want to!)

5. Too ambitious and eager for success

This situation is more common among people who come from training institutions. I don’t know if all cities are like this, but this is how it feels to me here in Guangzhou. It’s just that the goals are unrealistic and you don’t know yourself well enough! When I was in the group chat before, during the period of gold, silver and silver, many people were looking for jobs, and I met many people from training institutions while chatting. There are various proficiencies on the resume. I have just graduated and trained in a training institution for a few months. Either I have two or three years of work experience, or I have trained for a few months. My technical level is similar to that of people on the market who have two or three years. In short, you are bragging that you can do anything! But as soon as the question comes up, I don't know nine out of ten questions. When asked what a closure is, I don’t know; when asked what a prototype is, I don’t know. I asked what inheritance is, but I still don’t know. Here I have to talk about a question that impressed me deeply. I use this question to deal with those people! See which person is proficient in all kinds of things and boasts in all kinds of ways. I immediately asked this question, but no one could answer it correctly. The question is below!

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

What is said above is just a superficial phenomenon. More importantly, if you are too ambitious, it may make it difficult for you to find a job! Because some companies think that they can only give you a maximum salary of 4,000, but you think you have the ability to get a salary of more than 9,000. In this situation, it is difficult to find a job! It doesn’t make a good impression either! What’s more, it may affect your career choice! Personal advice: Start from reality and evaluate yourself. Think about what you know and what you can bring to the company! You can also stop at other people's suggestions and compare others' technical levels and salaries, or look for some interview questions online to see if you can answer those interview questions! Finally, evaluate yourself and where you think you are!

6. Avoid difficulties when you see them

I believe many people have felt this. During development, they encounter one or more needs or functions that they feel cannot be achieved. . Trying every possible means to escape, such as: This function is not very important, is it okay not to do it? I've never done this function before, and I can't figure it out. Outsource this function to others, we can’t do it! Lots and lots of escape words. You can think about it, if you escape every time, will your technical level still stay at the basic stage over time? How can I improve my technical level in the future? Personal advice: Face the difficulties head on. In web front-end development, if you encounter difficulties, it is normal. If you do not encounter difficulties, you are in trouble! When faced with problems, we should challenge them instead of escaping from them! Everyone wants to improve their technical level. Isn’t challenging difficult problems a good practical opportunity to improve their technical level? If you complete a difficult problem that you thought was impossible before, this is a testament to your improvement in technical level! No? I also feel that writing simple business code every day without exploring new knowledge or challenging difficult problems is not very interesting in development!

7. As long as it can be used, but you don’t want to optimize

This is also a very common situation. Many people think that the code they write can be used and it can meet the needs! I don’t care about future optimization at all. When it comes to developing projects or plug-ins, although I also advocate: implement first, and then optimize this method! But it doesn’t mean that I’m done with development and won’t think about optimization anymore! If you don't try to optimize your own code and explore better ways to write code, let alone write high-quality, concise code in the future, because you have blocked an important way to learn to write high-quality, concise code. Another thing is that in the project, some problems may be potential. Even if there are no problems in the project now, it does not mean that problems will not occur in the future. Instead, after the project is developed, try to optimize your own code, explore better implementation methods, and try to write high-quality, concise code. Isn't this a good learning process? As for the ways to optimize the code, there are many, many (for example, as often said: the code is too repetitive, should we introduce design patterns? The website performance is average, can it be optimized?), optimizing this area does not mean optimizing to the best in one step, but At least it won’t be worse than before! Regarding optimization, I have also posted some resources before. It’s easy to find, and there are many resources online! Just take a look!

8. Don’t ask if you don’t understand and ask immediately if you don’t understand

Don’t ask if you don’t understand. Everyone knows this. When you encounter problems, you never ask your colleagues or consult others through other means. Just meditate there and try various solutions. The worst result of this approach is that the problem cannot be solved in the end and colleagues will be asked about the development status. The best result is that the problem is solved, but it will definitely take a lot of time to solve the problem. If you don’t understand, ask immediately. This is what the word means. If you encounter a problem, ask others immediately. I don’t think much or not at all. This can solve the problem, but it will cause you to ask your colleagues frequently, which will make your colleagues very impatient. If your colleague's patience is worn out, the tone of your answer may not be very good. This will not only affect the relationship between colleagues, but will also make you afraid to ask your colleagues for advice in the future, putting you at the risk of not knowing and not asking as mentioned above. Personal advice: Ask for advice when appropriate. When you encounter a problem that you don’t understand, first think about it in context. Think about whether you have encountered this problem before. If you can’t solve it, go to the Internet to find a solution. If the problem has not been solved, then ask others, ask colleagues or through other channels. Ask others. In this way, I can think, my memory will be deep when solving problems, and I will not disturb my colleagues too often!

9. Pretending to understand if you don’t understand

This subtitle is similar to the above one on the surface, but in fact it is different! Pretending to understand when you don't understand means that when you ask others, you actually don't fully understand what others explain. Maybe it's because of face, or because you are embarrassed to bother others for so long, or you are worried about disturbing others for too long, so you pretend to understand. But this may fool you for a while, but it will soon be revealed again. This will make you have to ask others the same questions again after a while, which will make others even more embarrassed and embarrassed! You will also disturb others more time! Personal advice: If you have questions, ask someone else, as long as the person you ask is not a very impatient person. He will patiently answer your questions! Therefore, when asking other people a question, you must make sure that you understand the reason for the question. If your colleague fails to explain it clearly once, and you don’t understand the answer directly, I believe many people will explain it in detail again. If you are worried that your colleagues are busy with work or for other reasons, you can choose a suitable time! What I ask my colleagues now is, either don’t ask, or if you want to ask, just get to the bottom of it! Of course, my colleagues are very patient. Every time I have any questions, they will patiently answer them and even expand on them!

10. Write code without clarifying the requirements

After receiving the requirements, many people’s first reaction is to write code, even before they clarify the requirements. . Another situation is that many people think about requirements while writing code. This development method is in case you misunderstand the requirements! This may lead to a large part of the code you wrote having to be modified, or even completely deleted and rewritten. The probability of writing code without clearly understanding the requirements should be quite high, but generally speaking it is difficult to detect this situation. After all, it is normal for programmers to add, delete, modify and check code! I don't know myself, but the boss put it forward during a technology sharing. His suggestion is that for some slightly more complex requirements, first clarify the requirements, simply draw a flow chart, and then write in the code first A little comment, and then start writing code! Regarding this, I am currently implementing it! Unless the requirements are really simple, I will simply draw a flow chart on a scratch pad. According to the flow chart, write the comments and then write the code. This will be more organized and the code will be clear. There may be rework in the future, but it will not be as much as before! Both development time and efficiency have been improved!

3. Summary

I don’t know about the current market situation of web front-end in other cities, but Guangzhou is indeed not very good, and the competition is also very high. There are almost 100 people competing for one position, among which The reason is that there are many training institutions and the front-end entry is simple. Faced with such a situation, all we can do is to learn from time to time and improve our technical level. Only in this way can you ensure that you are highly competitive and can stand out from so many people. When it comes to learning and improving yourself, in addition to having a learning method that suits you, you should also learn from some learning methods that hinder progress! The above 10 points are some of my own thoughts. hope its good for U.S! The last one is, if there are any good or bad learning methods, please give me some advice. Let everyone exchange opinions and learn from each other!

The above is the detailed content of Veterans summarize 10 learning methods that hinder progress. For more information, please follow other related articles on the PHP Chinese website!