beginning
In Dachang, writing a good document is a very popular skill. This is not just an icing on the cake, but a weapon for many engineers to promote and build their own voice. My in-depth experience in the group in the past two years is that most of the powerful senior engineers (excluding those who are promoted on the basis of qualifications) have no ambiguity in writing documents, and they are able to grasp the superiors and project G point.
Some people may think that my skills are good enough. Why should I improve my ability to write documents? If I have this skill, I might as well look at the source code analysis? This is a common confusion among junior or beginner engineers. This is because most of the newcomers have a deep misunderstanding, that is, they think that doing software engineering is a job dealing with computers, but it is not. Software engineering is not just dealing with code, but more importantly, dealing with people. It is a very social job. In most companies, especially large factories, there are very, very large numbers of people and groups involved. In a small factory, the exchange of opinions and designs between people can be passed on by word of mouth, but once there are too many people, it can only rely on documents. Unless you are so good that one person can finish all the code, it is better to consolidate your own document writing ability honestly.
If you have the habit of writing technical blogs, congratulations, and I believe you have some understanding of how to capture the document audience. This will greatly help you survive in the big factory. Don't be sad if you don't have one, this article is carefully designed for you.
In this article, I will roughly list the skeleton of an Android project design document and some positive and negative examples that I actually encountered in my work, so that everyone can practice in the future.
1. Know what it is and what is its use
I believe that when many people are studying, they will find a complete set of materials on the Internet or buy a book to study, but the result is too much content, can't remember or half of the learning feels difficult, so they give up, let alone I have no way to start writing code.
And a better way is to not rush to buy books before learning, buy materials, first understand what the language or knowledge does, why this is there, what problems can be solved after learning, what jobs can be done, and it The history of development, so as to ensure that we learn the latest knowledge and have a general understanding of the future work direction.
After having this general understanding, decide whether you need to learn this knowledge.
2. Construct a mind map of knowledge
If you decide to learn this knowledge, you are here to construct a mind map of this knowledge. It can clearly show the knowledge structure of a language. We can compare the knowledge points on this mind map for targeted learning.
As for the production of mind maps, you can refer to the book catalog and some training websites to cover all the knowledge points of this knowledge as much as possible.
The following is my mind map of Android:
3. How to obtain information
First of all, you need to know what are the big cows of the language you want to learn. Start with a big cow. Look for books written by him, blogs and public accounts to find what you need. The so-called famous teachers make good students. Learning is not your problem!
Secondly, look for the official website and excellent community related to this knowledge. Visiting the official website and the community can increase your skills.
At last
Because there are too many questions and the workload of sorting out answers is too large, it is limited to providing knowledge points. Many detailed questions and reference answers have been compiled into PDF files. Small partners who need it can privately mail me [Interview] for free or click GitHub to get it for free !
[External link image is being transferred...(img-hlbxkpwW-1611544790856)]
