The "philatelic reading" approach to reading
I recently learned about a way of reading - philatelic reading". Many students who are learning something new go online or ask someone with experience to make multiple reading lists for them to facilitate their learning. Some big cattle seniors recommended the book list, the books in the book list are also classics, beginners according to these book list to start collecting books, many people will collect books after basically not read, better students will read one by one, but with little success, where is the problem here?
Many students don't read the right way， They address the book list， Read them one by one， Books from the book list will， one by one「 ransack」， Note the overturning here， Lots of classic books.， Knowledge is not something you go through all at once， understandable， as the ancients say： read a book a hundred times， its meaning is self-evident。 But many of us， Including myself.， For the sake of a moment of pleasure， Finished the book very quickly， For questionable points in the book， No deeper investigation.、 serums， No refinement， Without a spirit to break the sand.， Just to get through the book early， The above method of reading is "philatelic reading。 He makes us think we've read a lot of books.， But once the books are closed， We can't even recall what the point of the book is？ Not to mention applying the points in the book to life， It's on the job.。 So how do you solve this problem?？
Focus on practical effects
A hundred heard is better than a hundred seen, a hundred seen is better than a dry, when we look at a time there remember to take notes, the function of the notes is not only to review later, at the same time we can also be in the process of taking notes to appreciate the relationship between the knowledge points before and after, in the process of taking notes, we can also think, how to use the knowledge points. At the same time after learning the knowledge points to actively apply to practice, for computer programming work, practice coding is the most important, once away from the actual coding, it is really paper, I suggest that when you learn new knowledge points, you must open the computer IDE, in time to verify the knowledge learned debugging.
Outputs push back inputs
In the Feynman method of learning: teaching is the best learning, and if you feel that you have mastered the knowledge, you can actively tutor teaching to your classmates and consolidate your knowledge, killing two birds with one stone. This is the process of output pushing back input to the point where teaching is the equivalent of relearning and discovering your deficiencies so you can learn them twice later.
If there are no suitable teaching resources available, you can also summarize what you have learned into a blog and publish it on the Internet to gain the supervision of the general public.
Having said all this, I mainly want to say that reading should not be pursued only for the quantity of reading, while ignoring the quality of reading, without the quality of reading, more quantity is useless.
Finally, a piece of advice to everyone: read more classic books, books where the underlying technology is explained, because only when you have mastered the underlying core technology can you go further on that basis.