Make a good summary

Read a lot of books, but hardly ever made notes 650) this.width=650; "src=" Http://img.baidu.com/hi/jx2/j_0009.gif "alt=" J_0009.gif "/>.

On the one hand, because they are more "lazy", on the other hand is not so deeply aware of the importance of the summary.

Until one day ...

Find it impossible to do a new job.

Then consulted the group of senior, hope that it gave a summary of the document, and guidance one or two.

However, the predecessor of the document is very few, and fragmentation system. Yue, do not understand the question, practice makes perfect.

After a small demand, in the senior "detailed" explained the needs of the development process, I went to the fart to start.

My humble: Senior help me to see, here is how to report a model parameter error, what does this parameter mean?

Predecessor: This parameter means ... balabala .....

I: Oh, that is the meaning ah, I think there are other parameters I also smattering, there are no relevant parameters of the documentation?

Senior: I have a small sum of my own summary, but not all, you later fill the next.

My humble: Oh, well ...

PS: Seniors at least summed up a small part ... 650) this.width=650; "src=" Http://img.baidu.com/hi/jx2/j_0004.gif "alt=" J_0004.gif "/>

My humble: Predecessors, model documents I changed, help me to see why the compilation failed to read this tip information ah.

Predecessor: We use this framework after the model file modification is completed, you need to use the tool to generate some intermediate files based on the model file, before compiling the model file, and then compiling the code ...

I: Do you have a description of the relevant documents?

Predecessor: Not at the moment, you summarize one later.

My humble: ...

My humble: Senior, I developed, how to verify it?

Predecessor: XXX before summarizing a document, I will send to you later, there is a problem to find XXX.

My humble: OK.

Follow the documentation, after encountering a place that you do not understand ...

I: XXX, hello, I follow your written documents to carry out the requirements of self-validation, found ...

XXX: Oh, you said this situation I do not know how, mainly I did not do the relevant things, the document written in the content I do not remember now, forget how the specific operation of the. You can try other methods ...

My humble: ...

Finally, self-verification basic OK ...

My humble: predecessors, the requirements of development verification is over, you can go to the library.

Predecessor: Yes.

My humble: I have already mentioned the mergerequest.

Senior: OK, I'll give it to you later.

After senior approval mergerequest ...

Senior: Pclint ran over? Have you run past the use cases?

My humble: CI is not all integrated. I see, Pclint, but the use case seems to hang a few ...

Seniors: Debug the Use cases as soon as possible.

My humble: Ok ...

Senior: Oh, yes, I forgot to tell you that there are some other jobs you need to do, balabala ... and make up for it as soon as possible.

My humble: Oh, yes. Is there anything else besides these?

Senior: Well, there should be no more.

PS: In fact, seniors are in the group Daniel, often someone to ask him questions. In addition, he summed up a lot of documents, but for me this kind of novice lack of a bit of workflow-related guidance documents (in fact, predecessors also have a summary of relevant documents, but a bit old, and the existing process a bit inconsistent).

Until one day ...

My colleagues often ask me about git-related issues.

Colleague A: XXX, come and help me to see, I can not cut branches.

My humble: Is there any uncommitted changes to the current branch?

Colleague A: There seems to be.

I: Do not need to save the changes to revert off, need to save the first stash or commit, after you try again.

After a while ...

Colleague A: Yes, haha ...

Colleague B: XXX, I changed things on the master branch, there are many, I do not have permission to the master branch push permissions, how to do.

I: OK, first commit it, and then based on this pull branch on the line, and then with the new branch on the library, return to the master branch of the modification of the line.

Colleague B: This is OK?

I: Rest assured, next time remember to pull the branch ah.

Colleague C: XXX, I didn't use git, they let me find you understand the GIT-based development process, tell me about it.

My humble: Balabala ... Did you remember?

Colleague C: (a blank face) so complicated, is there a document?

My humble: no ...

............

............

Finally one day ...

I can no longer endure the frequent interruptions of my work by my colleagues ' inquiries.

Then a summary, advertised, and then asked a few.

This article from "Change a posture to see Knowledge" blog, reproduced please contact the author!

Make a good summary