javascript - Is there any way to memorize documents?
我想大声告诉你2017-05-19 10:39:27
0
13
1154
It is easy to get distracted when reading technical documents, and you forget what you have finished reading after a while. How can you improve the efficiency of reading documents? Can you remember it after watching it?
Technical documents still need to be verified through operations before they can be remembered, because often learning new things and the author's thinking are not on the same channel, and it is difficult to achieve resonance; unless it is knowledge you have already mastered and you can remember it just by looking at it. Verify it immediately after reading the document, and then it becomes your own thing
For front-end learning, practice is actually better than rote memorization. Documents are actually just for reference, if not necessary. Just remember that this API belongs to that JS library. Remember some characteristics and naming styles. So that when you check the API later, you just know where to look. . For example: _.findWhere When I saw this name, I roughly knew it was underscore or lodash
This is the same as memorizing English words - memorizing them by rote is meaningless. Only when you put them into context can you remember them better. 上下文中灵活运用时才能更好的记住。 js的代码自然也是，放到上下文运行环境 JS code is naturally the same. It is placed in Contextual Runtime Environment, which makes it easier to understand and remember in practice
Multi-purpose, but many things are subject to the 2/8 rule. 20% of the documents you read are the ones you need to use frequently. You must be completely proficient. The other 80% is the more proficient the better, but there is no way to check the documents at that time. Question
So when reading technical documents, one is that you must do it yourself. Unlike novels, which have storylines, it is easy to memorize them. Practice will give you true knowledge, and it can also help you remember important things. The second thing is not to see the whole thing at once, divide it into chunks and knowledge Click to take a look, or even read some other technical blog posts after seeing this piece of knowledge to take a comprehensive look.
Then you can understand which ones are 2 and which ones are 8. You will also master the things that need to be mastered and remember the things that need to be remembered. For the things that cannot be remembered, you will at least have an idea and you can learn them in 3 seconds. Find the corresponding place in the document.
What are you memorizing? Just know that there is such a method. Just check the usage when you use it. Programmers' brains should not be used to remember random things.
It needs to become your own thing, so you can write your own summary notes or the like. Even if you can understand this thing yourself, it means that you understand it and can remember it.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Remember it for what?
They say it’s a document, just preview it once and understand it.
Just check again if you need to use it in the future. Used in the same way as a reference book.
Technical documents still need to be verified through operations before they can be remembered, because often learning new things and the author's thinking are not on the same channel, and it is difficult to achieve resonance; unless it is knowledge you have already mastered and you can remember it just by looking at it. Verify it immediately after reading the document, and then it becomes your own thing
Read it over and over again, twice if it doesn’t work once, and use it, so you can remember it after you become familiar with it
To deepen the impression, you can only use it multiple times. . . Looking at fragmented information is not very beneficial to learning
For front-end learning, practice is actually better than rote memorization.
Documents are actually just for reference, if not necessary. Just remember that this API belongs to that JS library.
Remember some characteristics and naming styles. So that when you check the API later, you just know where to look. .
For example:
_.findWhereWhen I saw this name, I roughly knew it was underscore or lodashThis is the same as memorizing English words - memorizing them by rote is meaningless. Only when you put them into
🎜contextcan you remember them better.上下文中灵活运用时才能更好的记住。js的代码自然也是，放到
上下文运行环境JS code is naturally the same. It is placed in
Contextual Runtime Environment, which makes it easier to understand and remember in practiceMulti-purpose, but many things are subject to the 2/8 rule. 20% of the documents you read are the ones you need to use frequently. You must be completely proficient. The other 80% is the more proficient the better, but there is no way to check the documents at that time. Question
So when reading technical documents, one is that you must do it yourself. Unlike novels, which have storylines, it is easy to memorize them. Practice will give you true knowledge, and it can also help you remember important things. The second thing is not to see the whole thing at once, divide it into chunks and knowledge Click to take a look, or even read some other technical blog posts after seeing this piece of knowledge to take a comprehensive look.
Then you can understand which ones are 2 and which ones are 8. You will also master the things that need to be mastered and remember the things that need to be remembered. For the things that cannot be remembered, you will at least have an idea and you can learn them in 3 seconds. Find the corresponding place in the document.
What are you memorizing? Just know that there is such a method. Just check the usage when you use it. Programmers' brains should not be used to remember random things.
Practice will deepen your impression. Even if you translated the document, you will forget it if you don’t use it often
It needs to become your own thing, so you can write your own summary notes or the like. Even if you can understand this thing yourself, it means that you understand it and can remember it.