I have worked in a more working-scale IT companies, due to the leadership of the company's operating capacity is still pretty strong, the company may also have to survive. Large companies, and small companies with quality entrepreneurial companies vary widely, but was pursued by management, the development of standardization.
We all know that coding standards are important, the company should have its own coding standards, it is only right and proper that our company is so dry, set up their own company coding standards met, the first thing we think of downloading a left see the right, look, what you need, when you can not find what, or can not find a suitable, look at this here is not satisfied, not satisfied with where to look at that, you would need to write an own?
Write your own, not so easy, typesetting to regulate it, it can not appear typos, there must be a chapter ordered it, also need to comply with a standardized format company, right? You write something, we can not deal with, you hope to come up with a fine, it would have to be carefully written, we have been engaged in technology, not good at writing documentation, good at writing documentation is not good at doing the development, the development of people do not understand write specifications do not meet the company's actual situation.
Then write it yourself, because the hand is not good at writing documentation, on the other hand tend to have this kind of thing, leading to write out, a month later, written, nor is it as simple as that can be released, to lead the review, leaders also have to look at, you wrote is not justified? Will give you some additional recommendations, and then you change, let the leadership review, our company's leadership is actually very powerful, are workaholics, we pay up, will soon be approved and additional comments and so on.
Leadership is also seen, reviewed, and is not able to publish it? No, because this does not mean that everyone's views, but also to meet to discuss, often attend the meeting, it is the company's technology backbone, the backbone of these tend to be either something or busy not open, finally get together, it was all cattle, particularly large differences of opinion, have joined together, with excessive, there is a negative, fight to fight, but also open several meetings in order to narrowly passed, and even abortion.
We simply count the cost:
a more cattle were written a month, plus the leadership review, correction (cost at least 10,000 to go, right?)
The organization of close to 10 individual open five meetings lasting half a day (200 yuan a person to calculate bar * 10 * 5 == 10,000 yuan)
the cost of rent, the cost of the meeting room, we do not forget the cost of management.
We toss to toss, put forward a code specifications, but also costs spent 20,000 yuan into, is not I do not know, be shocked ah. You say your company's coding standards whether valuable? A small company, whether norms can do?
But we have another idea, the high efficiency of our work, do not always just kept on going with each other, more than giving up some of the ideas are too personal, everyone compromise with each other more than with the look, may open a meeting on it, think what specifications can also be written directly take over, a little tinkering on it, there would be no excessive cost, and at a later time to improve the process of continuous improvement is possible, you do not always have too much of an excuse, and even tried The method for manufacturing an excuse for everything.
For example:
" This is your lucky day norm norm, not our company's practices, the company's specification can be discussed in a meeting. ".
" This program is not writing about how publishing the specification, the specification did not require, I can not write so how? ."
These are able to engage in excuse of the dead, it does so every day, the company can be confused Okay?
In fact, the reason is very simple, Microsoft how to write code, and how to write code on MSDN, Microsoft's function names are so written, so we write is the most simple, the whole world can be broadly accepted norms, usually written procedure is also more attention some do not always create a written himself out, Microsoft did not say how much of the wording is good, we are so in line, but also easy and efficient.
Inadequate please pointing, in fact, a company's okay, it also depends on culture, learn to give up, but also compromise progress .
Reproduced in: https: //my.oschina.net/iwenr/blog/227882