Data center cooperation-insights

It has been a long time for data center cooperation, but it has officially entered the status in the past few days. As our cooperation becomes more and more tacit, we are not so happy. Dan gradually understands my graph, and he will not add his own method for building it, nor will he lose the picture I drew. My friends are getting more and more tacit. I want to share my feelings with you.

 

Proper "interplanting", never put it on hold

Before preparing for the Professional Course Examination in July, I began to draw pictures. At that time, I felt that there was no difference between the two pictures. I always wondered if I could be lazy and draw less pictures, saving me a lot of trouble. Therefore, I have been looking at the pictures while reading the pictures. After that, I will prepare for the professional examination-holiday. The pictures are basically put on hold. When I got back from the holiday, I calmed down for a few days and picked up my figure. Although I didn't draw much, I felt strange. I forgot my previous ideas and ideas, and finally I started from scratch.

 

Pay attention to details and contact demands

I didn't pay attention to comments when I first started drawing the image. As a result, I picked up the image for a while and couldn't even understand it myself, let alone others. The other aspect is that there is a huge difference in comments between the document and the code. Annotations should be fully written and should be detailed as much as possible, including every class, every method, and every variable.

 

This is because you are familiar with the data center, including most of its functions and processes. In the drawing process, always draw based on your own ideas. It was discovered at the end. Ah, I forgot some small requirements, and the returned entity cannot be changed to a set. No way, you can only manually add methods to modify it. However, these problems can be avoided. We always draw pictures with our own understanding, but do not pay attention to our needs.

Maintain document, diagram, and program consistency

Using the automatic document generation system simplifies our workload, but there are also problems. For example, it is difficult to maintain consistency between documents, graphs, and programs. These difficulties are often attributed to consistent information management. It is very difficult for graphs and documents to be made perfectly at once without modification. Each stage may have modifications that are either large or small. Therefore, we need to pay great attention to this issue. Otherwise, even if the system functions better, your documents will become a decoration, and the role of documents will be lost.

Good organization and coordination

The pictures drawn by the group leader are not for themselves, but mostly for their partners. Every programmer has his own habits and character, and the initial diagram is not perfect. Therefore, it is often different from the initial design. The team lead should promptly discover and correct the problem to avoid more serious consequences.

While doing a good job of organization and coordination, we must also properly control the work progress. No one wants to finish the task as soon as possible. Can be urged, but should be moderate. Master Sun Qing said: the more frequently you urge, the less your sense of responsibility will not prove your sense of responsibility, but it will show that you do not trust the team members, and it is also prone to dislike. I think it makes sense.

Cooperation continues and Learning continues.