How to quickly read and understand technical documents in English

As a programmer, to implement our products, we first need to select one or several programming languages, followed by the use of various tools and third-party libraries.

In this process, the download and learning of these languages, tools, and third-party libraries is unavoidable.

Download is generally very simple, but about how to use, I believe everyone will have a variety of learning methods.

But no matter how it goes, it comes to the official documentation.

Then the problem is here! At present, most of the official documents are in English, how can we quickly understand and use the official documents?

Today, to take their own learning methods, and share with you, I hope we can try to take less detours, as soon as possible to find a solution to the bug.

It is easy to say, the main 3 steps: 1, the first to be able to find official documents; 2, see Introduction or OVERVIEW;3, the remedy

How to find official documents

This is not a big problem for most programming languages and tools, and it's easy to find technical links or documentation on the official website.

So far, the only one I've ever met is a link to a CSS that's been linked to it for a long time: Https://www.w3.org/community/webed/wiki/Main_Page#CSS

But think about it, too, because CSS is the way it is made.

From this we can also learn that we often need to organize what we know, or understand, the classification and history of technology. This way, the next time you have a problem, you can quickly navigate to a particular technology or several technologies associated with it.

Quick understanding of document architecture

Most technical documentation has a introduction or overview section, which is not written casually.

The structure of the document is like the architecture we used to write code, from big to small, step-by-step. Especially English documents, because foreigners write articles are very silly, starting point is particularly low, is the use of a gradual approach, let you in-depth understanding down.

This is why I ask you to read official English documents.

So this piece of content, we should not casually look. One sentence a punctuation!!!

What if you can't read? This should be considered from two directions, one is English does not understand, one is the description of the relevant technology or background do not understand.

1. What if I don't understand English? This time can use Baidu, check the meaning of the word (only to check the meaning of the word). At first, if you find that there are so many words to look for, don't be afraid. Because of the different technical documents, it is written by different people. It is possible that you can easily read another technical document, but this one is completely out of your grasp. So, calm down, read carefully, and look slowly. When you're done reading it, you'll find that the chapters in the back are much easier. Why? Because the same technical document, basically a few people write, with the words and terminology are consistent, so we just need to know that he likes to use the English words are OK.
2. Relevant background or technology do not know how to do? Look at this piece of content and your concern about the part of the relationship is not big, if not small, it is better to ignore the past. If there is a relationship, then you have to understand this piece of content first. By the way, if you encounter this problem, your technology library has added a new skill.

Remedy

The next thing is easier, and when you're done with step 2, you already know where to find the information you need.

What if you can't find it? Then please repeat step 2, the so-called book read Times, its righteousness from now!!!

The last question, can you buy a Chinese book directly to see it?

The answer is yes, yes, but it's like eating foods that others have chewed, although the end result may be the same, but what if you encounter the same problems in other technologies later on?

Do you want to continue to buy books? What if the book hasn't been out yet? In fact, not too much need! In addition, the translated book may be aimed at the old version. Once the new version has the corresponding update, you do not know.

Unconsciously and said so much.

Finally, if the official website does not provide technical documentation? Let's see if there are any source code on GitHub. Also, by the way, if it doesn't even have technical documentation, how many people have actually used it? Go to GitHub (if you have one) and take a look at its star number.

How to quickly read and understand technical documents in English