Re: AWS Coding Styles (and about boring plain-linear text files in the end)

["Peter C. Chapin" <PChapin@vtc.vsc.edu>]

On 2011-01-18 02:02, Pascal Obry wrote:

> In contrary, I do like very much style guide for at least one reason.
> When you work in with a group of developer no one should own somehow a
> bit of code. A uniform indentation avoids : "this is my code", "this is
> joe part"... Everybody on the team should feel comfortable with the
> whole software. The style is not that important, but a single style
> across a project is if you ask me.

I want to echo my agreement with this. I'm working on a project with
several students, most of whom are fairly inexperienced. Having a common
style is very helpful. Instead of brow beating the students into a
particular style we've agreed to just follow what gnatpp does. We can
agree on a particular configuration of the pretty printer and then
everyone can conform to the project specified style by just pressing a
button in GPS. No arguments.

I agree with Adam that sometimes the results are less than optimal and
certainly not as good as *I* would do on my own. :) Yet having an
enforced style that can be easily applied with the help of a tool has
made the code base better overall.

Peter