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

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Tue, 18 Jan 2011 08:02:58 +0100, Pascal Obry <pascal@obry.net> a écrit:
>> Then again, I've never had much use for style guides, especially when
>> they're enforced.  I think I do a good job of being sensitive to
>> others who might read my source, and writing in a way that makes it
>> easier on them; sometimes strict rules can actually prevent me from
>> doing the best job of this, especially since the one who writes the
>> rules may not have thought about every possible circumstance.
>
> 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.
Good points and well justified (will note it in my mind).

And on my side, I feel guide-lines documentations comes as natural with  
design documentation (as part of it). It is also one of the easiest to  
start with when you at least want to give a seed to such documentation.  
This may also be a sign the author(s) cared ;) If I was to rate projects,  
this would be a constant criteria and I would give or retain some points  
based on the presence or absence of such documentation.

-- 
Si les chats miaulent et font autant de vocalises bizarres, c’est pas pour  
les chiens.

“I am fluent in ASCII” [Warren 2010]