News for hackers. Stuff that matters.
Re:Google C++ style guide by shin_lao on Thursday April 10, 2014 @03:23AM (#7564643)
It might sound like a good idea to precisely describe how code should be written, until you realize it's inefficient and useless.

Code coherence can be accomplished with more relaxed rules if you delegate more responsibility to your engineers.

Re:Google C++ style guide by adamnemecek on Thursday April 10, 2014 @03:26AM (#7564652)
> Code coherence can be accomplished with more relaxed rules if you delegate more responsibility to your engineers.

Please elaborate.

Re:Google C++ style guide by shin_lao on Thursday April 10, 2014 @04:06AM (#7564774)
I think consensus through code review is better as compilers and languages evolve. If you write rules for everything you spend your time checking for compliance and perhaps rewriting rules instead of relying on a more organic code quality assurance.

You also want your engineers to think by themselves instead of hiding behind a rules book.

Re:Google C++ style guide by cloudwalking on Thursday April 10, 2014 @05:01AM (#7564927)
Code style doesn't dictate what your engineers build, it just makes their code easier to review and maintain. Code smells, foreign conventions, and inconsistency all make reviewing and editing code harder.
Re:Google C++ style guide by skia on Thursday April 10, 2014 @05:03AM (#7564931)
Some coding style guides amount to an obsessive compulsive disorder. They focus on trivialities, like an extra space between parameters or the placement of braces around blocks of code.