Re: Bad coding standards

[Tucker Taft <stt@averstar.com>]

Georg Bauhaus wrote:
> ...
> I understand that Robert Dewar prefers strict stylistic
> unification, for reasons that he has restated in this
> thread, namely being advantageous for maintanablility,
> and fostering egoless programming.  What is missing in
> this argument however, is, I think, on what particular
> view this is based.  Is it true that egoless
> programming is a good thing, _economically_?

For what it is worth, rather than using the term "egoless" programming
I would opt for "team-oriented programming."  That is, by working
together, sharing code and moving about in the code for the
system as necessary to make things better, everyone benefits.

And based on anecdotal evidence, those who cannot follow the
project coding standards tend to be the loners who lack a team-oriented
view in other ways as well, and end up contributing less to the
overall success of the project, even if in the short term they
"cut" more code.

> ...
> Georg Bauhaus

-- 
-Tucker Taft   stt@averstar.com   http://www.averstar.com/~stt/
Technical Director, Commercial Division, AverStar (formerly Intermetrics)
(http://www.averstar.com/services/IT_consulting.html)  Burlington, MA  USA