WEEK2 about code specification and code review

1. Code specification

I think the code specification is necessary, and I would like to present my own rebuttal to the following four points:

• These norms are the result of a bureaucratic system that wastes everyone's programming time, affects people's development efficiency, and wastes time.

The first thing you should know is, what is the code specification? It includes not only code formatting, but also coding styles and other specifications, often involving indentation, whitespace usage, tab usage, annotations, naming conventions, line lengths, and language feature styles, such as whether to use optional semicolons ... First of all, in the team work process, it is best to synthesize each person's coding habits, so that everyone can easily read each other's code to facilitate communication and communication in the team. It's not a waste of time.

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

The artist's level of performance, if only on the norm, is clearly not a good artist, and can be made more expressive by the way everyone is receptive.

• Norms can not be forced to all, should allow many exceptions.

I think as long as it is not too harsh norms, or try to do all the same, at least others do not seem to produce emotions.

• I'm good at coding, you can listen to me.

To combine the characteristics of everyone, can not just rely on personal habits.

WEEK2 about code specification and code review