Four views on whether to have code specifications

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: The code specification is designed to unify the style and form of the code for everyone's understanding, which in fact reduces the cost of maintaining and updating the software at a good time.

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

A: Even if you think of yourself as an artist, the art of programming is not manifested by some small norms and forms. Obeying a code specification does not limit the creativity of a programmer.

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

A: Depending on the specific needs of some projects, there can be some code specifications optimized for these projects, but most projects should still have a code specification, because common code specifications still help the collective, and the benefits to the collective outweigh the optimizations that individual projects achieve through specialization.

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

A: Code specifications are generally not particularly bad, especially inconvenient programmer programming, so if some companies code is very poor, it is more than rewrite code specifications, it is better to change a company.

Four views on whether to have code specifications