Meeting after winter vacation Cooperative Development

During the winter vacation, we cooperated for the first time to complete the data room charging system project. This morning, Mr. Mi held a meeting with us to let everyone talk about their feelings.For more than a dozen people, there are some minor content!

 

The main aspect is document allocation during communication, understanding, and cooperative development.

Before development, project managers, programmers, and users must negotiate with each other about how to design a specific interface to satisfy users. Then we need to use a language that programmers can understand to reach a consensus on the system architecture. This language is UML.

During the development process, programmers should be responsible for the content they have written, and note the content clearly. On the one hand, it is convenient for others to read what you have written.ProgramOn the other hand, other members or other layers may use the classes or methods you have written. Whether others can easily use the classes you have written depends on your xml annotations!

Documents are indispensable throughout all phases of the project. We must also have documents for communication. No matter what we say, a document is required. Even daily morning meetings should be documented.

For document allocation, Every programmer should be able to understand what the project is to do and what the program is to do in the spirit of not letting everyone master the core documents of the project. Our programming is document-driven, and the content written by every programmer is written according to the document constraints.

 

The following aspects are discussed.

The abbreviation is not a new content, but it is very necessary to raise it. In this discussion, I remember that every industry has its abbreviation dictionary. We try not to use our own abbreviations. You can refer to the abbreviations of msdn, industry abbreviations, and so on.

Variable definition issues. It is not a new content, but it makes me more aware of the principle of minimizing the scope and the overall memory of functional modules. Variables used in a method should be defined in the method first, instead of being written at any time. This helps you better understand this function block.

Performance problems. A problem that is easily overlooked at this stage due to excessive attention to "sacrificing efficiency in exchange for Software maintainability and reusability. Although the data structure has not yet been studied, personnel bureaus in this area are required. It should be used as a basis for comparing the methods of choosing me or others.

of course, the content and depth of the meeting are much more than that, but these questions should attract my attention. In addition, I got in touch with some company things during the meeting. Such as the development meeting, the company's core documents (including abbreviations and documents), the idea of communicating with documents, and so on