Read what Google coding considers

I have read a lot of articles over the past few days. I feel deeply touched by the article "Why does Google execute strict coding specifications.

I have to admit that I used to think that coding standards are useless, and sometimes I think it is a waste of time for developers.

In the process of cooperating with another company to develop a project, I accidentally checked their code, unified naming method, concise description, and detailed parameter annotations, it took me a little time to understand their business logic, and I was accidentally shocked by the negligible coding specifications.

Sometimes we resist and reject something (if it is really good), maybe part of the reason is that it is still too long for us to feel its charm, so thank you, the city has moved, and we have to go through it.

On the other hand, the company also regularly reviews the code and explains the code specifications. However, over the past year, we have hardly felt the benefits of the code specifications, for a long time, you have to carefully figure out what the previous comments mean. Even Ctrl + C and CTRL + V are too frequent. Some Comments and code are similar, the family cannot enter their own door.

In particular, some people with comprehensive technical capabilities, high personal work efficiency, strong problem solving skills, concise, efficient and rigorous logic structure, and working experience in large companies, it is difficult for them to follow the rules step by step. They will feel that they are creating and enjoying themselves, and the additional shackles have severely bound them to play, and even affected their mood. Maybe their self-standards are better than the current ones, as long as everything is still acceptable, at least fortunately.

However, what if the encoding specification is totally unreasonable?

If so, you are in trouble: You are ruined. But this is not because of this absurd coding specification. This is because you are working with a group of idiots. Efforts are required to prevent a good programmer from writing excellent code by making code specifications ridiculous. This requires a persistent, calm, and watery brain. If this group of idiots can enforce codes that are not available, they can do many other silly things. If you work for this group of idiots, you are indeed ruined-no matter what you do, whether you have rules or not. (I am not saying that rare companies are managed by a group of idiots. Unfortunately, we have never been short of idiots in this world, and many idiots have their own companies .)

I was a little shocked when I read this article. Yes, it was easy for us to make such serious mistakes, complaints, various clutter, and various delays ..

 

Column of the author:Yan zhiqing
Column address:Http://www.itxxz.com/a/pangxie/2014/0629/124.html
The copyright of this article is shared by the author and the blog Park. You are welcome to repost this article. However, you must retain this statement without the author's consent and provide a clear link to the original article on the article page. Otherwise, you will be held legally liable.