Top 10 Reasons Not To Use Coding Conventions / Standards十大理由不使用编码公约/标准
Top 10 reasons not to use coding standards : 十大理由不使用编码标准 :
1. 1 。 Coding conventions are hard to remember.编码公约是很难记得。 Why would you, the superstar programmer, have to remember coding conventions?为什么你会,超级巨星,程序员,要记住编码公约? As a superstar you should be allowed to code-as-you-will and leave it to the minions to clean it up after you.作为一个超级巨星,你应该允许代号为您将离开它到minions清洁起来后,你。
2. 2 。 Coding standards gives manager’s / clients yet another reason to reject your product / solution.编码标准,让经理人的/客户,但另一个原因拒绝您的产品/解决方案。 Why empower them to evaluate you on yet another metrics?为什么,使他们能够评估你的又一指标? After all managers have been known to measure productivity by counting lines of code.毕竟经理已经知道来衡量生产力计数的代码行。 This isn’t fiction.这不是小说。 I had one manager who counted productivity with wc -l .我曾一经理算谁的生产力与碳化钨-升 。
3. 3 。 Coding standards are different for different companies.编码标准是不同的不同的公司。 So having a coding convention in companies reduces mobility of software developers.因此,有一个编码公约在降低公司的流动性软件开发商。 Why would you, as a software developer, want to reduce your mobility?为什么你会作为一个软件开发商,要减少你的流动呢?
4. 4 。 You can never agree on whether tabs are good or spaces are good.你不能同意就是否标签是好的或空格是好的。 And then whether it is four spaces or eight.然后,无论是4位或8 。 Deciding upon a coding convention means you have to participate in endless fights of both camps.决定后,编码公约意味着你必须参与,在无休止的打架的两个阵营。 Not to mention whether hungarian notation is better or polish notation.更遑论是否匈牙利符号是更好或波兰的符号。 Why bother?为何?
5. 5 。 Coding convention makes your code easier to understand.编码公约,使您的代码更易于理解。 That makes your job less secure.这使得您的工作安全性较低。 Maintaining good coding standard means your code can be understood by anyone and your project easily outsourced to some lowly-paid Indian’s in Bangalore (the horror!).保持良好的编码标准的手段,您的代码是可以理解的人,和您的项目很容易外包给一些卑微的工资,印度的班加罗尔(恐怖! ) 。
6. 6 。 Insurance against merger & acquisitions.保险对并购。 Your job is virtually insured if your project is worth something.你的任务是,几乎被保险人如果您的项目是值得的东西。 Nobody else in the whole wide world can decipher your code as you rigorously do not follow any coding standards.没有其他人在整个世界上,可以破译出您的代码作为你严格不遵守任何编码标准。
7. Oh yeah, I am doing exactly that . 7 。 噢,耶,我做的正是这一点 。 Imagine you are facing a strong opponent / competitor who questions your very capability to execute the project successfully.想象你正面临一个强大的对手/竞争者,谁的问题,您非常有能力执行项目成功。 You can easily bluff your way through as nobody can decipher your code to expose your bluff.您可以很容易地虚张声势您的方式,通过为没有人可以破译出您的代码以揭露您的虚张声势。 Then you can later correct the mistakes, or should you?然后你可以稍后纠正错误,还是要你?
8. 8 。 Coding standards does not increase shareholder value.编码标准,并不增加股东价值。 You can use this high-sounding phrase (and lie) to impress your colleagues or manager.您可以使用此高调词组(撒谎) ,使您的同事或经理人。 If your project is doomed then you may actually be right.如果您的项目,是注定那么您可能其实是不对的。
9. 9 。 Lack of coding standards is an in-built obfuscator of your source code.缺乏编码标准是一个在建obfuscator您的源代码。 Even if your code gets stolen (like Microsoft’s), nobody can make head or tail out of it (like Microsoft’s).即使您的代码得到被盗(如微软的) ,没有人可以使头部或尾部出它(如微软的) 。 Remember never to write code like Sybase or you will suffer when it gets stolen (by you know who).记得从来没有写代码一样,赛贝斯,否则您将蒙受时,得到被盗(你知道是谁) 。
10. 10 。 Coding standards isn’ta good conversation starter.编码标准不是很好的交谈精简。 You cannot impress your significant other (or hopeful) with it.你不能留下深刻的印象您的其他重大的(或希望) 。 Nor can you use it as a leverage to demand a raise.也可以使用它作为杠杆的需求提高。 So why bother?那么,为何麻烦?
Filed under提起下 Headline News头条新闻 , , Humor幽默 , , Java Software Java软件 , , PHP PHP的 | |
| |
RSS 2.0 2.0 | |
Trackback Trackback跟踪 this Article |此文章|
Email this Article电子邮件此文章
You may also like to read您也可以想读 |




June 2nd, 2006 at 6:26 am 2006年6月2日在上午06时26分
nice joke…maybe you should post also 10 reasons to USE coding conventions.尼斯的笑话…也许你应该也是10后的原因,使用编码公约。
June 2nd, 2006 at 6:56 am 2006年6月2日在上午06时56分
Thanks.谢谢。
> 10 reasons to USE coding conventions > 10个理由使用编码公约
I think someone already did.我认为有人已经没有。
June 3rd, 2006 at 3:28 am 2006年6月3日在上午03时28分
You could replace “coding conventions” with unit tests…您可以取代“编码公约”的单元测试…
July 25th, 2007 at 9:32 pm 2007年7月25日在下午9点32分
the author of this piece is all wrong作者的这片是全错
i have been in too many shops where this type of ‘thinking’ prevails:我一直在太多的商店,这类型的'思想'普遍存在的:
everybody thinks they are a star, but mostly they are not每个人都认为他们是明星,但大多是他们不
code doesnt mesh, doesnt read well, and doesnt factor well代码的doesn't网格,的doesn't读好,的doesn't因素,以及
arguments break out of trivial things, and solid design and time tested principles are ignored, neglected, or worse,deliberately broken because of the “I’ll do it my way” attitude论据摆脱琐碎的事情,和扎实的设计和测试时间的原则,会被忽略,被忽视,或者更糟的是,刻意打破,因为“我会做我的方式”的态度
this author just doesnt understand that software development has a life cycle beyond the individual programmer(s); as a manager, I have to keep the longer term interests of the company and it’s intellectual property in mind, and I do enforce coding standards笔者刚才的doesn't明白,软件开发有一个生命周期超出了个别程序员( ) ;作为一个经理,我要保持长远的利益,该公司和它的智慧财产权,在铭记,我做执行的编码标准
also, code reviews absent a standard degenerate into useless waste of time同时,代码评语缺席的标准沦为无用,浪费时间