How to read technical books

How to read technical books

For the students without foundation, we strongly recommend the introduction of video, but when you have a certain foundation, especially if you want to check a specific point of knowledge, positioning video is often less than turn books or Google convenience.

But even a good book, the wrong way of reading, does not produce good results.

Now most people read as if they were studying textbooks at school, a word of a word of the buckle, a knowledge point must be made clear and thorough, only dare to continue to read further down, and this way of reading is undesirable, the computer is applied science, in addition to the basis of the theory, 90% of the book is no need to delve into the details.

Suggestions must consult in the IT industry, the master of the work, they read a feature, is on-demand and read, when needed, when to read, do not need to take a pen, read a probably, use when can think up where to check on the line.

Different books, there are different ways to read.

We divide the software development book into four categories and suggest different readings (assuming you've entered the door via video)

Category one: Manual type: This kind of book would like to put every method of each class, or every command of each parameter is clear, most of what XX reference manual, XX encyclopedia and so are all belong to this type, our opinion is that this kind of book is the most unworthy to read from beginning to end, not even worth buying, Because you can actually use the API, or the Help document directly. This kind of book is used for checking.

The second category: Basic theory: Some of the classic structure in the field of software development, algorithms, design, analysis and other specific theories, it should be said that this kind of books is worth the time to study, because these will not change with time, is universal things, such as data structure, algorithms, graphics, design patterns , analysis mode and so on, but this kind of book is very hard to read, the suggestion is in the work spare time to study, or when it is necessary to study this algorithm, basically can. Do not give yourself too much psychological pressure, you are only the user of the algorithm, do not expect (or say not for a short period of time, for the study is to participate in the work of the people) themselves become the inventor of the algorithm, can use these algorithms can be phased satisfaction, and even the details of the implementation of these things can temporarily put aside, So the books are easy to read.

Category III: Operation Guide: This book will take you step-by-step to do the operation, from the practice of summing up the theory, all kinds of xx in Action, XX cookbook, etc. is belong to this type, in fact, many books have this aspect of the composition, but this kind of book operation is often lagging behind the software version, So in many cases, if you follow the instructions inside, will encounter a variety of problems, the occurrence of the operation does not go on, this time you need to solve the problem of the ability to refer to: "The problem of the way", in addition, and read the operation, it is better to watch the video directly and happy.

Fourth: Mixed: In fact, more than 90% of the books are mixed with the above three types of books, there are some basic theory, plus some API instructions, plus part of the Operation Guide, a book was born. For this kind of book, read the process should be able to distinguish which part belongs to what type, the use of different reading method can be.

In short, the need to carefully study the book on a category, that is, the classic theory of the book, for most of the other, video primer, and then view its rough, when the need to check, is enough.

There is another question, how to read English books. Of course, this is said that you have a certain basis of English (high school words are generally enough to read English software development book)

To read English books, the most important point to the first psychological this, there are many people think that their English proficiency is not enough, so do not dare to read English books, pay attention to what is said here is not afraid, not not. Most of them have not yet gone to war, and have been scared to death. Therefore, first of all, you have to dare to open English books, no one is born to read English, but if you do not read, certainly will never read.

First open the English book, Handy to be ready PowerWord, pay attention to this time do not give yourself too much pressure, thinking about the need to improve their English through a book, do not do so, you will be very tired and there will be a deep frustration, thinking that reading can bring you the technology and English progress on it.

In addition, it is recommended to choose a simple and easy to read English book at the beginning, do not choose too difficult, the English-Chinese reading effect will be better. English book is also very taboo to read a word to read, it is too tiring.

Take a book about JavaScript, for example, "Professional JavaScript for Webdevelopers", which is generally recommended to have a certain JavaScript base, and then you can try to read English books, It is not recommended to read when you don't understand JavaScript at all.

Read the suggested code-oriented, read the title carefully, skim the content.

Code-oriented, is to focus on reading each paragraph of the code, because there is a certain basis, so the reading code can feel what this paragraph is about, most of the time do not need to read the explanations in the inside, it will be easier to read.

Read the title carefully, to read the title of each section carefully, because as a good book, the title of the section must represent the content of this section, if it is already mastered, say, "JavaScript Variable", for variables we already know, There is no need to read it carefully. If one of the sections is not mastered, say, "JavaScript XML," that is what needs skimming.

Yes, skim the content, read it roughly, there are some words, some sentence patterns do not know is not related, as long as the code can be combined to understand the content is enough, but if there are some words and sentence patterns strongly hinder your progress, then we must eat him down, every day not much, gnaw a two or three sentence patterns, four or five words, In less than a few months, most of the English books on the market are not a problem for you.

In this way, to read English Help, API and so on, will be much easier. No, you can try reading the MySQL admin reference manual J

Summarize:

One day I read three SOA books and 2 hours of reading an English book. is to view the rough (Zhuge Liang Reading is also the approximate OH:), read the key to use, read the title, understand the entire structure of the book, is enough. To what extent. Anyway, if you want to do an effect do not know how to do, I already know where to check, hehe.

Of course, this is based on the premise that already has a certain foundation.

With the introduction of video, view its approximate, on-demand and check, psychological relaxation, happy to read it, to read technology books.