AVR-Chat

--- In AVR-Chat@yahoogroups.com, David VanHorn <microbrix@...> wrote:
>
> www.netrino.com/Coding-Standard

I sort-of agree with Jim, but not entirely.  I would also not pay $100 for this, but I'm not sure I'd even take the time to read it if it were free as my own coding style is pretty tightly locked in my brain now.  I agree that most programmers have a style of some sort.  In my experience, it's more often unconscious than conscious because their style is subject to drift that they are at a loss to explain.  However, I meet very, very few programmers who use style as a tool to reduce defects, cooperate with other programmers or to achieve anything other than to type fast.  In lead positions, I have often had everyone in agreement that the team should use a common style, that my style is good and, yes, here we go, we'll all do it that way.  I have yet to have anyone follow through with such a committment.  It seems that style, like requirements, designing before you implement, a test plan, etc., is something most programmers know they should have but rarely bother with when the rubber hits the road.  That's what I think.

Graham.