A Free Trial That Lets You Build Big!
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
Some of my learning habits (Part3)
By Liu weipeng (pongba)
C ++'s Luo Yun (Http://blog.csdn.net/pongba)
This article mainly describes some basic learning methods (especially reading.
1.When you are enthusiastic about one thing, let's get over the most difficult stage at the beginning of everything.. Everything is difficult at the beginning, because it is a time of soaring new knowledge that never understands the basic facts. At this time, it is the greatest difficulty. Some people can't get through it. If they think it's too difficult, they will give up. However, fanatic interests can offset the feeling of difficulties, so it is important to start a good start when you are enthusiastic about one thing. (Of course, this does not mean that perseverance does not matter ). Of course, this may vary from person to person. For me, I will be very focused on learning when I am very interested in one thing, and I will do a lot of groundworks. It will be better later.
2.You can refer to the topic rather than the topic.. I used to read a book before. I saw a book in my eyes. Now I read a chapter or even a section, what I see in my eyes is not a book, but a pile of chapters, a topic of knowledge, and reading by topic, you will find that when you read a book, you will not read another book honestly, but will jump from one book to another frequently, from one item to another, so as to obtain how different people explain the same topic. For example, I recently found that I checked 10 pieces of data when reading the Monte Carlo algorithm, including three or four paper and six or seven books. This is because even a classic book, you cannot expect that the introduction to each topic is perfect. Some books have a better introduction to a topic (knowledge point), and some books have a better introduction to other knowledge points. Sometimes a compact paper is better than a book. Books on my hard disk are classified by topic. Each topic contains a pile of books. When I need to learn the knowledge of a topic (such as Bayesian learning or Neural Network ), I will open all the books involved in this topic, index them to relevant chapters, and then read them well. So how can we determine whether a piece of information is good or bad?
3.Good information and bad information. Features of good materials: Starting from the problem, focuses on the concept behind the method (rationale), focuses on Intuitive interpretation, rather than the technical details of the method; according to the time flow of method invention (first, what problems are encountered, then how to analyze, reason, and finally find the current method ). Bad Data is characterized by the opposite of good data: the details of the method come up, as if a method fell from the sky, they often write "our definition... we name it... let's take the following steps... ". I don't want to explain why we should use this method. People first thought of this method because of the problems they faced, how they came up with this method, and what is the intuitive idea behind the method. In fact, if a method is expressed directly in the most concise form, the vast majority of information is often lost. The lost information is the thinking process behind the problem solving. As for why most books cannot do thisHereI tried to analyze it.
4.Before learning a theme, you first need to accumulate a full sense of doubt in your brain". That is, to find out what the problem is. Before browsing the method itself, you 'd better ask yourself what method you can think. A widely accepted fact is that the more you have doubts about the problem, the more you think about it before. The more deeply you feel when you see the answer. I remember that the textbooks in the university always put the entire knowledge structure in front of me in a simple manner. The reading process was quite cool. I nodded and soon forgot about it. Why? Because I have no questions to learn.
5.Selective reading. Many people think that I have a fast reading speed. In fact, I only read it selectively. The selection here is embodied in two places. One is to select the chapters of interest in a book for priority reading. Second, you can quickly skip a book that is technically weak or has a low information density. In general, in addition to technically powerful books, the information density of most books is very low and there is a lot of nonsense. In general, we should split the content like this during reading: 1. What is the problem? 2. What is the solution? 3. What is the example? If it is necessary to explain a phenomenon (such as Black Swan), then 1. What is the phenomenon? 2. What is the explanation? 3. What are the reasons for supporting this explanation? 4. What is the example? In general, this may not take many words (if only one or two excellent examples are taken). A typical example of such nonsense works is "Evolution of cooperation". so why do some books clearly show the core points of view (at most a few excellent examples) but write them to death? Because people's thinking has a "Lenovo" feature, it is easy to show off the text, and the author often feels that it is awesome to extend it out, sometimes a lot of theme-independent nonsense is involved; then, the irrelevant nonsense should be filtered out selectively during reading; there is also a possibility of a large number of redundancy examples. Generally, a well-organized book contains detailed and clear directories and indexes. You can filter out a part of the contents of a sub-chapter (for example, you have read the contents of a sub-chapter before ), then sometimes the author will give a lot of redundant examples, if you have already been impressed by these examples, you can simply not read them. (Some books are very generous, and each point of view is supplemented by one or two of the most classic examples, for example, "Psychology of difference-how to face psychology", I like this book most ).
6.Why not?? If you do not understand the knowledge, there are several possible reasons: 1. You do not have enough effort. The ancients concluded that the book had read its meaning for a hundred times. Although this rule is not always true, it can be fully explained from the perspective of cognitive science. When we read it, attention tends to selectively pay attention to some of the "points", while ignoring other "points". As a result, it may be unable to understand the whole because of some omissions. Or you can simply ignore some of the details but important things. In addition, it takes a certain amount of time for the brain to understand something. The processing speed of the brain is very slow, and the neural impulse transmission speed per second is only a hundred meters. Finally, we may look at a sentence from a specific perspective due to our mindset and ignore the possibility of understanding it from different perspectives. In this case, I read it twice more carefully and try to understand it twice more! This is the case ." Suddenly realized. 2. It involves concepts you do not understand. This is technically incomprehensible. In this case, cross reference is required. If the concepts you don't understand are used in one sentence, you can check them. Now many books are e-books, and you can search for them directly. For paper books, you can just check the index at the bottom of the book. The strange thing is that many people simply give up without analyzing why they don't understand it. Just like solving the problem, the problem cannot be solved. The first thing to do is to analyze why the problem cannot be solved, rather than directly asking for help. 3. The order described by the author is incorrect. You may see the previous one later.
7.How to get a rough assessment of the quality of a book before reading. The ability to quickly evaluate the quality of a book can save a lot of time before reading it in depth. There are several clues: 1. Read the author. The books written by the author are generally good. 2. Check the Directory and description. A good catalog and introduction can reveal a considerable amount of information about the quality of this book. Whether the directory structure is clear or straightforward (rather than playing tricks) is a measurement clue. 3. when you look at the rating on Amazon, we should note that apart from the overall score, we should also look at what the people with the lowest scores say, because niche opinions may often come from people who are actually knowledgeable (except those who come to kick the pavilion ), if you don't see any really valuable counterargument In the opinion with the lowest score, it's pretty good. 4. See the sample chapter. Amazon generally allows you to randomly browse some chapters to see whether the expressions are clear, whether the arguments are rigorous, and whether the content is profound. This can be seen on several pages.
8.How to find a good book. Several clues: 1. Same author's work. 2. Amazon-related recommendations and topic-related book columns (similar to bean columns of Douban ). 3. A good book (or a good piece of information-whether it is a book or a webpage), other books highlighted in references. 4. Sometimes, for a topic, you can find reference resource guidance summarized by good people, which is the best.
Start building with 50+ products and up to 12 months usage for Elastic Compute Service