Whether code specification is required

1. These norms are a waste of time in a bureaucratic system that wastes everyone's programming time and affects people's development efficiency.

A: For example, I just contact the person who wrote the code, not familiar with the code, spend a certain amount of time to standardize their own code, the specification code can not only unify the style and form of code for everyone to understand, but also reduce the maintenance and update software time good cost, so that we can have more time to improve their own things, So I think code specification is not a waste of time affecting efficiency.

2. I am an artist, a craftsman, I have my own norms and principles.

A: In the development team, each programmer must have the same specifications. If each programmer has their own style, all according to their own specifications to write code, then this program in the final run, there will be a lot of problems that require everyone to spend a lot of time to find the problem of the place to waste time to affect the efficiency.

3. Norms cannot be enforced, and many exceptions should be allowed.

A: There is something special about anything, depending on the particular needs of some projects, there can be some code specifications optimized for these projects, but most projects should still have a code specification in common, because the common code specification is still very helpful to the collective, This benefit to the collective is even better than the optimization achieved through specialization of individual projects.

4. I am good at coding specifications, you can listen to me.

A: For those of us who are new to the code specification is necessary, so that can form a subtle convention, we all default to a specification that can greatly shorten the time to write code, in other people to check the code can also be convenient and quick to find the problem.

Whether code specification is required