Introduce code quality reviewer in project management

 

Some problems have been encountered in the author's software development experience over the past few years, especially in the development of a highway engineering management and performance appraisal product in the previous two years, I have been thinking about these problems and looking for a solution. Now I have some ideas and hope you can make an axe.

Here, I will only elaborate on one aspect, which involves a narrow area, but is still universal.

In software development, especially in product development, there is a problem that the code is easy to understand and the code style is inconsistent, and the code quality is not high, as a result, it takes a lot of effort to hand over the work for personnel replacement, which often leads to project delays or even failures. In addition, low-quality code also brings a lot of problems to the later maintenance work. In my opinion, to solve this problem, you can introduce the role of code quality reviewer in the project.

The code quality reviewer must perform the following responsibilities:

1. Review the programmer's code and mainly check the comments and descriptions so that you can understand the program structure and functions without the help of the programmer. If you cannot achieve this purpose, it means that the programmer's comments and descriptions are not enough to write. You can work with the programmer to complete these contents.

2. Check the style of the program code so that each programmer's code style is consistent with the given standard style. This is also an important means to ensure the ease of coding and quality.

3. Perform unit tests with the programmer's code. After all, programmers can look at the problem from a certain point of view. Instead, code quality auditors can perform unit tests in more aspects to improve the code quality. With unit testing tools such as nunit and JUnit, you can perform tests quickly.

In traditional software development, the above three aspects are generally completed by programmers themselves, but it is very difficult to complete these tasks by themselves, in addition, due to the existence of issues, inertia, and time, these tasks are not completed well. However, if you separate the work and hand it over to someone else, it can be more effective.

Of course, this will certainly increase manpower for software development and may not be suitable for some small projects, but in some large projects or products, due to the long development cycle, it can provide better quality assurance.

The name of the code quality reviewer may be inappropriate. If you have a better name, don't forget to tell me.