As we all know, the front end has made a revolution in recent years. The front end is also a learning curve in programming. In China, at least, there has been an explosion in the search index since the second half of 2013. You can look at the data: Baidu index, Google index.

On the one hand, new knowledge is constantly changing the impact of the front end, on the other hand, all kinds of new people rush into the front end field crazily. The impact of these two new streams, but a lot of tech community, q&A sites, such as: SegmentFault.

When you open the SegmentFault, the front end of the q&A stream (including Node) will account for half, if not nine out of ten. Even on StackOverflow, the old q&A site, javascripts were the most popular.

I am a person who likes to answer all kinds of questions, wandering around the SegmentFault. The most frequent front-end problems I’ve seen over the past few months are as follows:

  1. React/Vue/React is not correct.
  2. Framework-related UI and plugins, such as ElementUI and how to use components, vue-Router and other issues.
  3. Javascript this points to issues, closure issues, array looping issues, etc.
  4. Webpack, NPM and other engineering related configuration problems.

So what’s wrong with these problems?

Ninety percent of the problems can be queried through documentation. And most of it is not a remote, small corner of the document, but rather a long document on issues such as vue’s parent-child component communication.

Issues such as this direction, closures, and other syntax issues are the basics, and most of them are covered badly by blogs on the Web. To understand it, you can search it with your eyes closed.

There are also many repetitive questions that can be answered by searching the Internet.

What phenomena do these problems reflect?

  1. Yeah, the front end is hot, bringing in new people.
  2. The front-end geeks are learning the new technology stack that’s popular right now.
  3. But the study of basic knowledge is mostly ignored.
  4. And I don’t know the right way to ask questions.
  5. Even some excessive hand party.

Why is that?

Here’s my guess:

  1. A lot of people learn the front end is not interested in the front end, but feel that the front threshold is low, the market is hot, so learn the front end. No interest, less patience, less patience, less want to see documents, books.
  2. There are also some newcomers who were not born by professional classes, resulting in a complete lack of understanding of the programming learning process, that is, by asking.
  3. The training class also has POTS. They claim to be able to master the front end and take down big companies in weeks. As a result, front-end learners are eager for quick success and instant benefits, thinking that proficient operation of VUE is proficient in the front-end.
  4. Front-end freshmen themselves are very eager for new knowledge, because after a period of training or self-study, they find that they have not mastered too much knowledge, which is not competitive in the market. So it would also seem to be in a hurry.

If you happen to fit the description above, be warned, you are already on the wrong track. The front-end threshold is low, but the learning curve is not short. You don’t need vUE to get a good job.

I once heard a student said that his goal is to master Vue and slip away, I strongly disagree.

Probably a lot of new people are also this idea, but I know, most people say the mastery, writing slip, is not the real mastery. It’s a matter of memorizing documents, getting familiar with syntax, and understanding the life cycle process. Learning VUE is very good, but the real learning it is not to learn how to use it, but to in-depth study its design concept, implementation, read and understand the source code.

Unfortunately, you probably can’t read the source code at all. Why is that? Because you don’t have the basics. So your goal is off the rails. The goal should be to master Javascript itself first. On top of that, you can claim to have mastered Vue.

So what is the correct learning posture?

Start with the basics, HTML, CSS, JS -> ES6, these are enough to eat a pot. How to learn? Read their references and get the basics.

At the same time, we can use these vUE frameworks to do some engineering project practice. If we don’t understand something, we don’t need to go too far, because it will waste a lot of time. When you grasp the basics of a certain stage, suddenly look back, will suddenly enlightened.

After the basic mastery, the tool can also be used proficiently, and can even master it quickly. How to study further after that is not discussed here.

In addition, when we learn a tool, we should know the most basic person is what? For example, learning Vue, first will introduce it is the MVVM framework, if you do not know MVVM, how to learn Vue?

I occasionally see questions about how to get data from a DOM page in vUE. The original was using Vue and developed in the same way Jquery manipulates the DOM. That’s because you don’t even know what you’re using.

I know there’s a lot of front-end knowledge, like Node. Enough for everyone to eat a pot, will inevitably encounter problems, can not solve. But it really needs to be solved before it can be implemented. Inevitably questions will have to be asked.

So what’s the right pose to ask a question?

  1. When something goes wrong, the first thing to think about is documentation. Most of the time, we encounter problems because we use the wrong posture, exactly how to use, the document may have written clearly. For example, if I want to change the value of the parent component in the child component of vue2. X, an error will be reported if I change the value. What should I do? How to do? Check the documentation and it’s clear.
  2. What if the document cannot be found? It is true that sometimes problems are not exposed or clearly described in the documentation. At this time, we should search the question on the Internet first. Where to find? Google, the Issue of the project itself, Baidu although everyone does not like, but really to search Baidu is not wrong.
  3. What if no one else has? If it is the tool itself, the first thing to think of should be to look at the source code, the source code is really do not understand or understand, and then to ask questions.
  4. Some other business implementation problems, they really do not have the ability to achieve, you can ask.
  5. But asking questions is not only about solving immediate problems, but also about improving your problem-solving skills.

The fifth point, I’ll just leave it alone. Sometimes I see the best answers to questions that aren’t really the best answers. A lot of subjects just want to help them solve the problem. Some answers don’t give the code directly, but give a good idea or explanation, or a better design, or links to relevant documentation.

It is better to teach a man how to fish than to give him a fish, but some people only want ready-made fish.

Write in the last

So, after witnessing a lot of stupid questions, I finally gave a shout out: answering questions won’t save the rookie. I hope this article can slightly let some real love front-end students, better to learn front-end. Take doctrine, not to take other people’s code, but to take other people’s knowledge.