+1 Coding style is part of the corporate identity of the code, in a sense.
Regards Felix Am 04.03.2014 um 09:49 schrieb Thomas Mueller <muel...@adobe.com>: > Hi, > >>>> Question: why don't we use the maven checkstyle plugin? >>> for what? we are quite liberal in coding style and respect personal >>> preferences. the only checkstyle rules that make sense are the ones >>> that find or prevent bugs (like avoiding .* imports). > > Sure, the exact formatting rules are a matter of personal taste. But why > do companies such as Google *enforce* specific rules? > > http://google-styleguide.googlecode.com/svn/trunk/javaguide.html > > > Becase most of the time, developers *read* the code. And it's not just you > who reads your code, but everybody else as well. Formatting rules help > people read the code. I personally have a hard time understanding code > that doesn't follow basic coding conventions. In fact I dislike such code. > If you read a book, you expect certain formatting rules (identation, > whitespace usage, and so on), and if those rules are broken, you can not > concentrate on the content. > > In addition, some code conventions avoid bugs, for example the recent > famous Apple SSL/TLS bug: > > https://www.imperialviolet.org/2014/02/22/applebug.html > > With decent rules, and the Maven checkstyle plugin, it's easy to avoid > such bugs. > > Therefore, I think we should use strict rules. > > > Regards, > Thomas > > >
