The foreword 0.

On Friday, a WeChat friend sent me a message like this, asking me what should I do in the current situation of 996?

I said, well, you’ll have to figure out what to do, but continuous learning must be the key word.

So the question is, 996 times, how do we keep learning?

After thinking about it for a weekend, I decided to write an article to share my thoughts. It might be helpful for a common front-end developer like me.

Pay attention to the public account “front-end trial” reply “learning method” to obtain the complete map.

To sum up, it is the most important for everyone to find their own learning methods.

1. Active and passive learning

When we were at school, we had a set time to study every day. We had teachers to guide us and answer our questions. But when we get to work, all this is gone, and we need time to study between moving bricks.

We divide learning into active learning and passive learning:

  • Passive learning: learning on the job because of objective needs (such as implementing product manager requirements, designing a technical solution, job-hopping interviews, etc.)
  • Active learning: subjectively push oneself to learn for personal growth (such as reading books, articles on official accounts, source code of community open source projects, etc.)

We can also distinguish between active and passive learning in terms of purpose:

  • Passive learning: improves the ability to solve problems in order to eat
  • Active learning: improve the core competitiveness, in order to better eat

Passive learning

Let’s take a look at how to master the pace in passive learning and find the right method. This is mainly divided into two aspects: job and interview.

2.1 work

At work, there are generally two types of learning scenarios: demand and output.

  • How to implement this requirement
  • How do you implement this requirement more elegantly
  • How do you design a technical solution
  • Summarize best practices
  • How to debug, read logs, and locate problems
  • .

In summary, it is a question of how to solve problems at work. On this basis, we will try to summarize it, output.

  • How to use XXX to solve XXX problems
  • Best practices for XXX
  • Deep Learning XXX
  • The application of XXX in XXX
  • .

The process of summarizing must be a process of learning.

2.2 the interview

As anyone who’s ever interviewed knows, preparing for an interview can be exhausting, with a lot of input going on all the time.

2.2.1 Knowledge summary

Every review is a good learning opportunity.

Summarize my front-end knowledge system

The process of summarizing the knowledge system is a process of searching for gaps and filling gaps. When you don’t know or understand something, you must understand and make it clear, or you won’t be able to master it.

Summarize the projects you have done

  • Difficulties and highlights
  • The technical architecture
  • Best practices
  • Dig through all the technical points involved and see if there are any that you can’t describe

2.2.2 brush problem

Needless to say, it is to brush LeetCode: sword refers to offer, Dacheng question bank, induction and summary.

2.2.3 back problem

It may not be a very elegant word, but it is necessary.

Many knowledge points of front-end theory and methodology still need to be forcibly memorized, because you will not memorize particularly complete theories at ordinary times.

The process of reciting questions is another process of making up for gaps, because you have to worry about whether the interviewer will ask you about what you recited.

2.2.4 checking

Go to the interview round, review the interview process, and look up any gaps. Summarize the interview questions, clarify your thoughts and refer to the answers.

3. Take initiative to learn

Here are a few approaches that most front-end developers use to actively learn today (⭐ is recommended) :

  • Books: ⭐ ️ ⭐ ️ ⭐ ️ ⭐ ️ ⭐ ️
  • Community: ⭐ ️ ⭐ ️ ⭐ ️
  • Official account: ⭐
  • Paid for knowledge: ⭐
  • Training class: ⭐

In this article, I’ll describe the pros and cons of the different approaches, and how I’m learning now (key approaches).

3.1 the book

Think about their graduation is not a long time after reading?

The book has its own gold house, the book has its own Yan Ruyu

As a front-end developer, you might actually have good access to books after you work. However, books can provide complete theories and methodologies, through which we can systematically learn knowledge of a certain field, which is very helpful to the depth of personal knowledge.

Especially some computer basic knowledge, very suitable to learn through reading, such as data structure, operating system, algorithm, network and so on. This theoretical knowledge will not change over a long period of time, and you can safely pick up a very famous and highly regarded book and plough through it without worrying about its timeliness. It will benefit your entire career.

The purpose of reading is one: to break the casserole and learn to the end, to become the king of theory and to guide practice.

3.1.1 Key methods

3.1.1.1 How to choose books

What books should I read as a front-end developer?

First of all, front-end developers themselves are in the computer field, some of the above mentioned computer basics related books, are worth reading. Then there are some of the more popular front-end books in the industry, such as the Little Red Book, the Butterfly Book, JavaScript you don’t know, and so on.

I buy a lot of O’Reilly and Turing Books, which are really worth reading. Of course, other publishers are also very good books, so I usually read the recommendations of the industry leaders, or just read the books that are out recently, and if I’m interested, I’ll buy a book.

Pay attention to the public account of “front-end trial”, reply to “book list”, you can get a book list sorted some time ago.

3.1.1.2 How to store books

Dangdang and Jingdong often have very powerful activities, generally can be less than 50 discount to buy books, more attention to attention is good.

If you don’t want to buy it, you can only rely on luck, pay attention to the front end of the public number, such as the “front trial”, often have to send books to participate in the activities, maybe more.

Turing Community books usually have a gift card on the back. If you save up a few gift cards, you can redeem the books at Turing Community.

3.1.1.3 How to read

Schedule your reading time

Like an hour a day or a chapter a day

Look at the directory

Read the table of contents first to get a sense of what the book is about, and skip sections you already know or are not interested in

Write Reading Notes

A good memory is better than a bad pen. It is better to remember when reading.

It is recommended to record your thoughts in the form of a map.

Remember, don’t take notes just for the sake of taking notes. Focus on the content. The notes are an aid.

Combined with the practical

The paper come Zhongjue shallow, or to start the actual combat.

Technical books usually come with a lot of code, you can follow the rhythm of the chapter to start the code, deepen the memory.

Learn to summarize

After you have finished reading the book, you can review your reading notes and summarize the reading notes for the whole book.

Remember to publish the summary in the community, and communicate with people to discuss, writing can be very satisfying. There are several ways you can expose yourself:

  1. Contributions to the “front-end trial” public number
  2. Post the article to the nuggets community
  3. Register a public number to output their articles
  4. Share the article in various technical communication groups

3.2 community

The community here refers to some social platforms and technology communities, including GitHub, Zhihu, Nuggets, Twitter, etc.

The key words for learning through community approaches are two:

  1. Continuous attention
  2. Select the essence

Also here’s a summary of a few communities I often use (⭐ is a recommendation index) :

  • Making: ⭐ ️ ⭐ ️ ⭐ ️ ⭐ ️ ⭐ ️
  • Zhihu: ⭐ ️ ⭐ ️ ⭐ ️
  • The Denver nuggets: ⭐ ️ ⭐ ️ ⭐ ️
  • Twitter: ⭐ ️ ⭐ ️

3.2.1 making

Follow some of the more active ones and see their daily news.

If he stars in a warehouse,

  • Click on the Readme to find out what the warehouse does
  • You can write a DEMO to play with if you’re interested
  • If it’s possible to use it in the future, star it back to make at least an impression
  • .

If he follows someone,

  • Click on it to see if the person is active
  • There are well-known open source projects
  • There is still a very frequently original blog
  • .

To be precise, it’s about discovering something new on GitHub through Big V’s eyes and expanding your horizons.

3.2.2 zhihu

There are also many big Vs on Zhihu. What we need to do is also pay attention to the dynamics of these big Vs, and we need to get the following:

  • They often express some opinions, through which they can understand some knowledge points that they normally do not pay attention to
  • High quality original articles
  • New wheels or new toys
  • .

3.2.3 the nuggets

The nuggets is a hot front-end community in the country at present, there are still a lot of articles worth reading.

We can scour the recommendation stream on the front page every day, take the best of it, and find high-quality original articles.

We can also keep an eye on some of the big V’s, many of whom will often be outputting the Nuggets.

3.2.4 Twitter

Twitter is dominated by big V’s, who often talk about a technology direction, a new tool, or an interesting idea, just to see what they’re “playing” with.

3.2.5 Key methods

Keep paying attention, accumulating, and being curious.

Usually see what technology related content, you can click to understand. If you already know it, close it. If not, look. If it can be useful for you, save it. As the saying goes, collection === to learn, also is not without reason.

3.3 the public no.

A lot of people think that the public number can not learn, I want to say is that they just didn’t find a way.

First say the characteristics of the public number:

  • Fragment reading. Because of the form of expression of the official number, it is suitable for commuting, before sleeping, after eating and other fragments of time to read.
  • Active touch. The official account is pushed to the user through the form of push, that is to say, as long as I pay attention to the official account, I will receive the article push, do not have to worry about because of “lazy” and not to learn. That’s what we call “a big meal.”
  • Not “feed the pigs.” Public number and now popular short video is different, it is not a recommendation algorithm, you can see all aspects of the article through the public number, expand the field of vision

3.3.1 Key methods

Through the official account learning, I summarize two key words:

  • Focusing on the
  • continuous
3.3.1.1 focus

Pay attention to 1-3 front vertical domain public number

Get in-depth front-end articles, latest news, best practices, etc., for depth.

Pay attention to a public account in the field of computer

Get some articles in the computer field, expand the horizon, for breadth.

Don’t waste time on tidbits and headlines

Don’t waste time on spicy chicken articles, like skipping these headlines:

  • The XXX jump off a building
  • XXX yearly salary 80 w
  • Do you really Promise
  • 2021 will be too late to learn Node
  • .

Don’t pay attention to the current technical public accounts that don’t work for you

This type of public number will have a negative impact:

  • You’re prone to anxiety. I can’t even read it. Why do I eat so much?
  • A waste of time. I’ve been looking at it for a long time, but it doesn’t work.
3.3.1.2 continued

Decide if it’s worth reading by the title

Ditto, don’t waste your time on spicy chicken articles. Grandstanding headlines are more likely to be headline party than good articles. Of course, it just means that the probability is high. Because now the community is very volume, not an attractive title will not be seen, the original author is really difficult.

Judge whether it is worth collecting by the content

  • Do you need to read in depth?
  • Are they likely to be useful to them in the future?
  • Is it a solution, a best practice?

Mobile side fragment reading

Due to the limitations of the screen and scene, the Mobile terminal decides that it is impossible to read an article in depth. What is recommended here is to scan the content of the article roughly to understand the main content of the whole article.

PC side in-depth reading, classification collection

After reading fragments on the Mobile side, if you find the article useful, spend some time on the PC side to read it in depth, and classify and collect it, so that you may use it in the future.

3.3.2 rainfall distribution on 10-12 recommended

Recommend “front trial” public number

  • Front-end vertical domain public number
  • One technical article a day: in-depth reading, latest news, best practices, interview tips, etc
  • Technical exchange community/personal tutoring

3.4. Pay for knowledge

Paying for knowledge has become very popular in recent years, with all kinds of training courses, columns and video courses popping up one after another. This is actually a double-edged sword, good courses can lead us, bad ones waste time and even mislead us, we need to look at it in a correct way.

First of all, it is reasonable to pay for knowledge. There is no free lunch, think, why do others teach you for no reason, and then roll him? So, if you want someone to teach you something, you have to trade it for something else. Of course, the price should not be too high.

Secondly, we need to take the essence and discard the dross. Not all paid knowledge is worth it, some are good, some are really hot.

3.4.1 Key methods

First of all, don’t be averse to paying for knowledge. If you are interested in it, buy it if it is helpful, and don’t waste money on useless courses. I still spent a lot of money to buy the course these two years, may you say I am “leek”? But I did get what I wanted out of it.

  1. Directed search itself requires systematic knowledge points. For example, when you want to learn Webpack, complex configuration and process, if someone can systematically guide, it is very good; For example browser principle again, this thing is very abstract, do not have actual combat experience, need to have experienced seniors to summarize for you
  2. When it is recommended to plant grass. Don’t rush to buy right away. Open the catalog or recommendations first. What does the course cover? Is it patchwork or system? Can you use it yourself (look up gaps, expand your horizons, best practices, etc.)?

One small Tip is that most paid courses have a way to share cash back or discount codes. Such as:

  • Geek time: cash back part of the money, and have occasional activities
  • Nuggets Booklet: Find promo codes, or other activities
  • Pull hook column: new class return cash, or other activities, 1 yuan into, do not buy at full price
  • . And so on

3.5 Long-term training courses

Is not recommended.

If you’re really lost, or if you’re a career changer, give it a try.

4. To summarize

This article is spent one afternoon of time, whim to write, I hope you have some help.

More articles welcome to pay attention to the public number “front-end test”, access to front-end selected articles.