read technical books

My own thoughts on reading technical books or documents

   (PS: I used to read a book just because I thought it was awesome, but it was painful and inefficient.)

2. Don’t take notes when reading

   because taking notes will make the brain lazy Hint: It's okay to not remember, I made notes. Secondly, the speed of writing must not keep up with the speed of reading and thinking, and it is easy to get distracted in the time difference between. There is only one situation that can be considered, that is, the problem is too complicated, and the required cache exceeds the brain's Cache. At this time, you can draw a flowchart or something on paper to help clarify the problem. (At this time, because the brain turns very slowly, there will be no time to wander.)

   (PS: How to review without notes? Most people will not read even if they have notes. Re-learn when you need to review. Because there is a foundation, the speed is very fast)

3. Reading technical books or documents is a process of quick reference.

   Generally, every time The subtitle of a section is a question, and what we're going to do in this section is answer the (implicit) question posed by the section title. Quick lookup is where you find the answer to the section title question in each subsection. Since all of the books I read are knowledgeable, for me, this process is really a search, and I rarely need to think about it. If you have already found the answer, it means that you have grasped the main line, continue down, don't dwell on the details. If there is a problem later that requires previous knowledge, you can go back and check.

   (PS: Will this not understand enough? The understanding must be problem-driven. Without better questions, there will be no deeper understanding. If you don’t know prototype chain inheritance, how deep can you understand Java’s inheritance? ?Conclusion: Even if you memorize the whole book, you still don't understand it. So if you solve the problem, you understand it)

4. When you encounter background knowledge or terminology you don't know

   In fact, it's like encountering a word you don't know. If you can guess what it means, don't stop reading. If not, you can go to the Wiki. But when you come back to the book, simply review it and put your ideas together again.

5. Conjunctions Howerver,Otherwise, Except for

   If you find that the author's conjunctions are all reasonable and reasonable, I believe that it will not only read quickly but also be very pleasant.

Looking for a job, QQ: 2593632798