The meaning of code specification

1. Whether code specification is required

Consider the following arguments and refute/support for whether you need to have code specifications:

1. These norms are the result of the bureaucratic system of wasting everyone's programming time, affecting people's development efficiency, waste of time things.
2. I am an artist, a craftsman, I have my own norms and principles.
3. Norms can not be forced to all, should allow many exceptions.
4. I'm good at coding, you can listen to me.

First of all, for the above four points, I refute 1,2,4, about 3, I personally think that this exception should also be a limited exception.

At the beginning of the code, the teacher told us to develop a good code style, not only for themselves in the later reading can be easy to read, but also to facilitate the reading comprehension of others. Especially in team work, if everyone is very casual in their own way, not only bad maintenance, and can not understand the meaning of the code. This instead delays the workload, wasting time and reducing efficiency.

Http://www.vaikan.com/the-conventions-we-follow/in this article we learned about the code specification, which includes both the coding style and other specifications, not just the code format. And as for why we want to emphasize code specifications, we can also learn about the pros in this article. 1, adhere to the coding style to make the code easier to maintain, 2, coding style to form the collective code, 3, coding style can eliminate those long-term disputes. These are obvious. For a team, each of us is just a member no one is an absolute dictator, because cooperation so we have to take care of each person's style, such as point of view 4 This idea is not only in the code to cooperate with this idea, and others are tired of the tyranny.

Just like the inadequate surrounding area, if everyone insists that their code style is not standardized, then it is more annoying to have conflicting views when the code is handed over. The waste of time is much more wasted than when it comes to norm-setting.

http://www.vaikan.com/things-everyone-should-do-code-review/in the process of code review, you are only paying the time without harvest, the process of review is also re-learning the familiar process, As you review your companion's code, you also learn about other people's design ideas, and also help you improve them completely.

The meaning of code specification