Readers often ask me this question, indicating that there is too much to learn on the front end, and then give me a list of technology stacks: what are the three major frameworks, various family buckets, applets, UMI, FLUTTER, SSR, Node, etc.

There’s a lot of front-end stuff, but there’s no need to learn everything. Once you get that idea, you’ll probably fly around like a chicken with its head cut off. Look at this, learn something about that, and you end up learning nothing.

Examples: actually, I saw in the readers better, study does seem to be in the study, what data are collected, watch this video technology, today tomorrow take another technical books to read, but this way of learning is quite inefficient, what data is collected also can cause the appearance of a completely not enough use. If you don’t have a learning goal plan, you will only get half the results (maybe not even half the results). Because part of programming is a lot of coding, and if you learn it today and watch it tomorrow, you don’t end up learning anything well without a lot of practice.

What do you want first

Knowing what you want is one of the things you have to do before you start studying, otherwise you’re running around with your head cut off.

If you really don’t have any ideas, here are three ways to do it:

  1. Foundation, anyway no matter what scene below I can recommend learn foundation first, foundation is bad to talk about other is play rascal
  2. Learn the stack of technologies your company is using or will use in the future
  3. Look at the requirements of large companies (remember, they don’t require you to learn a lot, only small companies will require you to learn a lot), and then pick out the requirements for which you are not proficient

Depth or breadth?

In fact, this question personally feel that there is no absolute answer, both have advantages.

Digging deep helps you become an expert in a field, although most people don’t have this opportunity, but we can certainly do more than some people, so digging deep can help you become the industry is not so easy to eliminate.

Exploring breadth will help you to understand more concepts and so on, and the other person will feel that the more you learn, the faster you will learn. Of course, the breadth of this exploration is not the kind of practice to learn everything mentioned above, but in learning a direction of the time with the related content also learn a little.

For example, if you’re going to start learning Redux today, you might want to take a look at some of the advantages and disadvantages of Redux as you learn it. The important thing to note here is that you are not required to learn all of its competitors, but to learn the strengths and weaknesses of its competitors (that’s breadth), and to dig deep is to learn Redux until you can build the same wheel (that’s way down).

Building a knowledge system

It’s important to build a body of knowledge, because otherwise whatever you learn is a separate piece of knowledge, and it’s easy to forget when it’s not connected to the rest of the material.

You should have seen such things as front-end knowledge brain map on the Internet before, this is actually a kind of secondary point (because this is just a division of a subdivision, not related to more subdivision) knowledge system, of course, it is also great to master it first.

The better way is to connect as much of what you learn as possible with other knowledge, as much as possible.

For example, when the interviewer asks you about theoretical knowledge today, it is a good knowledge system practice if you can present theoretical knowledge first, then related theoretical knowledge, and finally describe this knowledge with examples from your work. You’re connecting this theory to other theories, but you’re also connecting it to actual examples.

So how do we build our knowledge? The method is simple:

  1. Write down what you have learned in your own words
  2. Draw a brain map and condense your notes into a brain map
  3. Repeat steps 1 and 2 to learn new knowledge, and then consider whether the new knowledge can be related to other knowledge. If there is a connection, use arrows to connect the two directions

Don’t try to learn everything

Many of the technology stacks listed at the beginning of this article, such as FLUTTER, SSR and UMI, are actually not familiar to many of the authors, but I will not always think about when I will learn them.

Because the person’s energy is limited, for the work in a big probability with less than what I have always strategy is to learn about the technology stack, read the Readme, know just what it has solved the problem, in addition to this won’t continue to learn, only when I really need these technology stacks I will learn to them.

I recommend this strategy as well, because there’s really no point in getting too far ahead of yourself to learn a technique you don’t know when you’ll be able to use it. As I said before, programming takes a lot of practice. If you don’t, you might forget it a little bit after a while (I will anyway), and then after a while, you might have to relearn what you have learned before you use it. It’s not good to have that time to play games

This article is formatted using MDNICE

Wechat scan code to follow the public account, subscribe to more exciting content Add the author wechat group chat technology