How to read documents quickly and efficiently!

作者:极客小俊
把逻辑思维转变为代码的技术博主

insert image description here

introduction

程序员It is common for us to read technical documents, and
even if you are not a programmer, no matter what industry you are in,
there will always be time to read documents, articles and books...
So what kind of reading method can quickly absorb the technical documents All knowledge and essence?
How to avoid inefficient looking at documents? When you see the later content, you forget what to do with the previous content?
And the most important thing is to quickly apply it to the project after reading the document?
These are the questions we need to consider when we read the document!

insert image description here

Determine the problem to be solved

Establish good problem requirements

clarify your purpose

If you don’t even know what is the purpose of learning a technology? What business scenarios can it be used in, and what does it have to do with you now, what kind of results can you get in this situation? You must know that you don’t have 问题需求to read the documentation, it’s true Troublesome way to read!

But if you have a clear one 问题和需求, the reading goal at this time will be completely different, and of course the effect will be completely different!

No matter what kind of document you are reading, or a thick technical series, I feel that some people just pick it up and start reading slowly from scratch, and then they can't stick to it after a few days PDF文档. Purchased online, even some people may have never started ! Because of 无从下手confusion!

That is because whether it has been established in the heart 问题需求模式, the gap between the final result and the generation of reading technical books and documents without any problems and reading documents with a certain target nature is one world and one underground!

Core thought process:

  1. Want to know that the technology you are currently learning is a 什么thing?
  2. Learn a language, or a technical framework, system, etc... to know it 为什么exists, and its role and application scenarios
  3. The last is to figure out how to master the important technologies and knowledge points

insert image description here

​ Of course, it is estimated that some people will also ask: (我根本无法去想一个我不了解的东西 应该去如何学习?)that means that the previous one 1、2两点did not understand, and there is also a lack of basic understanding of a thing! Here we have to talk about 百度this vocabulary again. The easiest way is to search directly on major platforms, find As soon as I look for relevant information, just like this, a normal person can basically understand what the technologies and frameworks I am learning are what, their functions and application areas, and after a little understanding, they will be more targeted. Sexual and directional reading of the document and selective reading of the book focus!

小结: So with the above problems, cognition is required to 基本建立have a sense of direction in reading documents and technical books! Otherwise, for ordinary people who are not academic masters, there will be a mess in their minds!


Human energy is limited

insert image description here

Don't spend your time and energy on useless things

​ We need to know one thing, life is limited after all, and everyone 时间和精力is also limited. For some junk information, we should avoid and block it. After a long time of accumulation of junk information, big data will continuously recommend some garbage and useless information. Redundant data is given to you, making you feel like you are learning but not learning anything. Therefore, you should grasp the key information, and reading documents is the same as reading books. You should pay attention 方法to them, so as to save time and learn what the documents are in the fastest speed 精华!

Build your own technical knowledge architecture system

insert image description here

We want to 有限build on what you've learned in as little time as possible 知识体系框架, always following 项目问题and需求主题

Sort out the technical points obtained from the learning summary with a more logical relationship framework, and add them to your own knowledge framework system!

Of course, in the final analysis, we should not forget one sentence, and 学习、阅读we should all follow the same principle:知其然,还要知其所以然

How do you know what you've learned is correct?

cross-validation

The reason is also very simple, just find more relevant information and discussions, and summarize them together, and you will 技术点have a comparative 全面与深入understanding of this! Because after all, different people 技术点will have different understandings of one, but the same five people There are 3 people who 技术have published similar statements about a point, so the result is correct in most cases!

技术点In this way, you can basically find what you need by reading a document or book.

insert image description here

Summarize and improve

insert image description here

Or 文档is it enough to read it? It is definitely not the case. It is very important to use the actual project development and application scenarios, that is, all the knowledge needs to be applied to the actual project to demonstrate, but there is an important point, that That's it 善于总结!

Why have a summary?

As the saying goes: 好记性不如烂笔头For you to read a technical document or read a book, the ultimate goal is to learn something! But if you really learned something, then should you write a paper or blog to summarize what you have learned things? Or if you have spare 时间time, you can tell others the knowledge you have summarized. If others can understand what you are saying, then you have really learned the knowledge; If you can't express these things to others, then you can conclude that you probably don't fully understand them. So in the end whether you have figured out what you have learned, you can tell by a test.

In fact 总结, there are actually many ways and means. In the process, we will rebuild our own technology and knowledge we have learned, and unknowingly improve our knowledge reserve, and our knowledge system structure will also be enhanced! You can see what others have concluded. 框架文档、api、PDFThat is also summed up by others, and you must have your own system!

In short, when you can 轻松输出learn the knowledge points by reading the document, then this is called truly understanding a document!

Guess you like

Origin blog.csdn.net/windowsxp2018/article/details/119012978