[bikamonki]

I'd say yes but don't get too strict about it. It is common sense and the key point is readability. Long lines are hard to read, avoid them. Meaningless variable names are hard to follow/read, avoid them. Un-indented code is hard to read, avoid it. Shorthand statements are hard to read, use them but train your programmers to use them. Break long/big functions into smaller ones. Agree on files/directory structures. In my company we've never used hard rules, mostly common sense, and I think it's working.

As long as readability is working for everyone, rules that are too picky like camel case vs underscore, indent with tabs vs spaces, etc, will just add overhead.