In the software development experience of the author, especially the development of a road engineering management and a performance appraisal product in the first two years, I have been considering these issues, and I've been finding a solution. Now I have a little idea, I hope everyone ax is.
Here, I only explain to one aspect, and the surface involved is narrow, but it is universal.
In software development, especially in the development of products, there is such a problem, that is, the easy-to-readability difference between the code is inconsistent with the code style, and the quality of the code is not high, thereby directly leading to a lot of time, it takes a lot. Energy, and often lead to the project extension or even fail;, the low quality code has brought a lot of problems to post maintenance work. I think that to solve this problem, you can introduce the role of the code quality auditor in the project.
Code quality auditors need to perform the following responsibilities:
1. The programmer's code, mainly check the annotation instructions, so that you can understand the structure and functionality of the program without programmers. If this purpose cannot be reached, the programmer's comment is not written, and it is not written enough to match the programmer to complete the content.
2. Check the style of the program code to make each programmer's code style consistent with a given standard style. This is also an important means to ensure code readability and quality.
3. Combine the programmer's code for unit testing. After all, the programmer is a certain angle, it is not possible, but the code quality auditor will perform unit testing, and the code test can be improved in more ways. The test can be made quickly through a unit test tool such as NUnit or JUnit.
In traditional software development, the above three aspects are generally done by programmers, but they are difficult to do this, and because of the perspective, inert, time factors, etc. Work is not good to do. However, if you separate these work separately, give it to some (some) people to do, you can play a more effective role.
Of course, this willness will inevitably develop people's hands, may be inappropriate in some small projects, but in some large projects or products, due to the longer development cycle, it can play a better quality assurance.
The code quality auditor This name may be called unsuitable, everyone has a better call, don't forget to tell me.
