How to read technical books

 I do not know if you have this feeling? When you get ready to read a book and, in a few days always wanted to read it in; you do not want to see the back turned forward; how many pages each day to read the book as a measure of their value today, and is not absorbed much knowledge; read a book always feel empty head, looked back in front of the forgotten ...... of course, you may still run into a lot of trouble reading, here I am to talk about their reading Some of thinking.

  First of all here to do first assumption, the assumption must read the book in your hand is a classic, great book. If not, then quickly throw, a good book is a good teacher, and a slag book simply kill people ...

  Then I put the book Computer roughly grouped into three categories:

  (1) book language. Such as C, Java, Python, etc.

  (2) algorithm books. "Introduction to Algorithms", "Programming Pearls", etc.

  (3) a particular type of book. Such as operating systems, compiler theory, network, Linux kernel, server principle and so requires a lot of effort to completely master the book.

  Of course, this classification is very shallow, different kinds of books for our reading strategies will be emphasized.

  First class for the first book. The trick one word: practice.

  As a novice, do not fall into the minutiae of the language, the way some people learn language is really a dilemma, for example, he wanted to learn Java, he took a hard look at java programming ideas, forget looked back in front, the unbearable pain of their practice, the last sigh: Java sad to say! (I witnessed ,, also more than one or two, but also drunk). Others, from the Internet or somewhere and got a number of instructional videos, then tilted his legs while sitting on that side seemingly "attentively" look, half-way up the people but also occasionally QQ chats (Dude, when you are watching What movie?). Both look different learning styles, in fact, is essentially the same, is a passive acceptance of the way of knowledge.

  In this way and inefficient, remember: the code is knocked out, not to see or hear out! Whether you're reading a book or watching a video, in fact, does not matter, the key is that we must own hands to knock it out. After reading the book or watching a video, you should have on hand a lot of code, then the code this time knocking a dozen times, then your mind is leaving the code instead of text or voice.

  Having said that, I think our English ,, personal feeling is the most effective way to learn English is placing themselves in an English environment or create yourself an English environment, the next is hard to say. . Thus, within a few months, to ensure that your English Bang Bang da! Rather than desperately look back words or grammar. . (Well, do not Tucao English the O (∩_∩) O!).

  The algorithm then talk about how to read the book. The trick: understanding + application.

  Learning algorithm is different from learning language, learning algorithm is the most important thing is not memory, but to understand. On how to understand the algorithm that has nothing to say, and look at each person's perception as well as adhere to, of course, go online to find some information easy to understand, or will you discuss with the students learning algorithm is very helpful.

  We focus here to talk about why should emphasize use. Because the algorithm is inherently more difficult to understand this kind of thing, more difficult to understand what it is relatively easy to forget, for example, you finally took a long time to understand a dynamic normalization algorithm or KMP algorithm, and then you think they've completely mastered, then throw in a few months whether it. Then there is no then the ......

  So algorithm Once you understand the important point is that the future must go use, to use in different scenarios. So in the end how to use it? For example, the back of your algorithm book exercises, there are many colleges and universities now have a good ACM OJ, a large number of algorithm design problems above, these are very good resources. When you use the algorithms you already understand the problem to the solution algorithm, the process itself will further facilitate your understanding of the algorithm, and strengthen your memories. For example, it might take some time you forget this algorithm, but when you think of a solution for you that question, you recall again that the algorithm. Because we human brain is not always easy to remember those abstract concepts, and for those specific things remember more prison.

  Anyway, the use of algorithms to solve problems is very time-consuming, and sometimes half a question you might not have AC. . So I suggest that those students are now still reading, if you want to go the way of the future IT technology or algorithm to learn it. You are absolutely good! After work you might want to learn no time!

  Finally, learn to talk about the third category of the book.

  The third class of books usually are some highly theoretical book, more difficult to digest, but the short term can not see what is the value. For many programmers feel irrelevant. But we can say: to understand how deep this type of book decided you are a lion or a siege program ape.

  Of course, everyone has his own choice, not everyone wants to go very far in technology this way, if you want to be that technically achievements of their own people, then welcome to explore together. If not, then when casual look better.

  The characteristics of this type of book, I summed up my own reading method - three times reading method. Yes, that's right! At least three times. For these books, or do not read, read to read at least three times. In fact, in reality, there are a lot of people read the book for themselves are not willing to go to read, whether it is technical books or other aspects of the book. This may be with people to see too utilitarian reading about, go read the book think reading is a waste of time, might as well read a new book.

  If you ask a person why you want to read a book, he may tell you to learn new knowledge or acquire new ideas. Indeed, the aim is indeed true, but often he ignores a simple truth: If a book is read only once, then you can only absorb up to 10% of the knowledge. If you read the second time, third time. . . You will be able to absorb knowledge has grown exponentially, and then when you read on, you have not just simply re-absorb knowledge the book itself, you will form their own thinking, maybe this is an old saying of reading a hundred times , its meaning from it now!

  So, if a classic book brought, you are only prepared to see it again, I still do not look, sheer waste of time! If we talk about a good book to read it several times, then the question is: How do I read the book it? Repeat from head to toe look or are there other methods? Of course. Why do I want to mention here three times to study law, which is actually a trade-off for input and output, and no one knows Duokanjibian better, but the reality is often very difficult to give you enough time to see repeatedly, this time you need to find a way can be as much as possible with the least amount of time to get the most out of.

  So three times reading law specifically how to operate it? If you get a technical book

  First pass

  End the book as much as possible in a relatively short period of time. In the first pass, do not fall into a specific knowledge, which is again the main purpose is to be able to grasp the important points of each chapter, remember, is to grasp, rather than a thorough understanding. This is again the emphasis is on fast and efficient. Do not drag too long. And for the first pass after reading the "results" to keep in mind, the best record it, because they are the backbone of the entire book.

  Second time

  The second time the emphasis is slow to understand. The second time must be slow to understand the point of knowledge as much as possible, do not be too fast, do not pay attention to the progress. Remember, in this one pass: Haste makes waste! Experience really do not understand the point, can be put off, and so on come back to see the back of understand it, or ask someone else.

  Is not recommended to take notes while watching the best at reading each chapter or after the holiday, the books together, then you've seen that part of the memories in my mind to go, especially in knowledge is the key point, then put it down, so much higher efficiency than simply taking notes. (Personally recommend a blog. Do not feel that their level is not enough, I am sorry to write a blog. Remember, not only to write a blog for others to see, more important is the consolidation of their knowledge learned on the point of an idea usually this sort are very efficient. in addition, newcomers often think to write blog very time-consuming, but believe me, if you really intentions in writing blog, it will not disappoint you in these times!) so once completed after you've got a more complete understanding of the entire book. This time, you can go and see you write your own blog, do not worry read the third time.

  Third time

  If you usually earnest read a second time, you may be put off. The human brain still need some time to digest slowly, even if it is subconscious, moreover, in a short time to read it several times in a row does make people feel tired. After such a period of time (for example, to look at some other books ah, etc.), then you start to read the third time, I believe that this time you are feeling very relaxed (who tend to have a pleasant sense of familiarity knowledge), this time you not only consolidate the knowledge you before, and there might even let you generate new ideas, such as when you put the theoretical knowledge of the operating system almost all of them, you may wonder exactly how it works, you will the impulse to want to read the kernel source. This course into another realm of it! (When you studied the theory books look at the source code of the operating system, you can even know what to write well what was written dregs of it! (^ O ^) / ~).

  Finally, I have to say, even for these highly theoretical book, to really have to understand that they also need hands-on, such as the operating system can try to learn to see the source code, you can try to make their own learning compiler theory a small compiler, learning network theory can go to build the network environment to deepen the understanding of the network and so on.

  Lu borrow the famous line: paper come Zhongjue know this practice is essential!

  Of course, these are just some of my personal thoughts on reading, not necessarily right. Everyone has their own way.

Guess you like

Origin www.cnblogs.com/dylancao/p/12234341.html