About code quality assurance

Where software companies haveCodeLibrary, VSS, CVS, etc. This is the most basic protection of the company's code, but the changes to this code library are different from the company's control. As far as I know, some software companies in China can freely modify code in the code library as long as they write code (Dev, effecect, PM, you can control the code library only when the product is about to be released. This does not guarantee the code quality of the code library. We know that every company'sProgramPersonnel levels are uneven (of course, companies such as Google and Ms may need to talk differently). The level is high or low. If the quality of the checked-in code is not controlled from the initial stage of the project, to improve the quality of the Code is just an empty talk.

A good practice is to revoke the programmer's permission to sign in the Code and only grant high-level experienced personnel the permission to check in the Code. General personnel must pass their review before checking in the code, if the review is passed, it is checked in. If the review fails, it must be modified until the pass is unknown. In this way, you can control the code that won't be checked in from the source to ensure the quality of the Code. Of course, this may sacrifice efficiency, or even get used to it at first, but the benefits of this approach are obvious as long as you stick to it. For the company, too.