Today's miscellaneous

1.Requirement understanding

All members of the project team have a meeting and ask the required personnel to explain their needs. The programmers can understand the Meeting on the spot and ask questions they do not understand. Although it can let programmers know the needs, it seems that the work efficiency is low. In turn, this sentence should be: although the work efficiency is low, the method is stupid, but it can let programmers know the needs. In fact, it seems that no better solution can be found!

2.There is basically no design evaluation, so that programmers cannot control the coding quality and level. Design is very important and necessary, not just the overall design, local design, functional design, and interface design. The system should be designed and evaluated.

3.Coding and Reconstruction

Reconstruction should be done at the design level. The encoding staff should rebuild their ownCodeIt is equivalent to checking homework during reading. This check not only checks right and wrong, but also optimizes it.

The Code should be very careful and responsible. It is not easy to achieve this. To be lazy and omit some judgment and conversion, the system is not robust and the problem is hidden.

Special attention should be paid to the variable check in coding. In fact, the robustness of the system is whether you check the system variables completely. The principle of independent governance should be followed. Independence means that the check of variables does not depend on any external forces. Division of governance means that each of them manages its own variables.