Standards and Egos (was RE: ILE Propoganda)

Interesting view.. devil's avocate's hat sported...

> -----Original Message-----
> From: Chris Rehm [mailto:javadisciple@earthlink.net]
> Sent: Saturday, June 23, 2001 12:39 PM
> To: RPG400-L@midrange.com
> Subject: Re: ILE Propoganda
> 
> 
> I think the biggest problem is programmer's ego. The thing 
> is, standards
> always involve compromise. But, there will always be 
> programmers who feel
> that doing things the other way is the "better" of the two. 

This is true.  Can't argue with you here.  But, are we talking about
programmers and programmers arguing standards, or programmers and
management?

If the first, the most of the time a conflict exists because of one of two
things.

1.  Someone doesn't want to learn or use new techniques
2.  Someone thinks they know more than they really do

If it's the second case, then it may be a case of management using their
"power" for the sake of flexing their "alpha status" (yet more ego). 

These days, it's hard to find management that should be making any sort of
technical descision in the first place.  Not every shop is like this, but
it's moving that way.   But I digress.  ;)  

So, in this second case, it is the ego of management that is the problem.  

> Since they are
> no doubt "smarter" than the people who had to make the 
> decisions in the
> first place, they violate the standard. Obviously this really 
> proves they
> aren't as bright as they thought, since they are taking 
> actions which cause
> the most harm overall, but their ego isn't going to allow 
> that to sink in.

What is worse?  Keeping your bright programmers at the level of those that
don't want to learn anything new, or letting your bright programmers set
standards?  Who will be less satisfied in the long run?  Who do you want to
feel like a team player, the go-getter or the "I just work for a paycheck so
don't make me learn ILE" person?  Who do you want on your side, working for
you?

Standards are always changing.  Let's assume a shop doesn't use ILE.  If
someone starts using it, writing functions, etc, for a "proof of concept" is
that bad, or good?  (none of this "if they go off on their own it is!" crap
either, let's assume the proper channels are taken.)

> 
> The thing is, programming using standards is an act of 
> teamwork to allow the
> whole shop work together more effectively. For programmers to 
> do that, they
> need to be able to set their ego aside. Really, we all program with
> standards. Just the egotistical among us only accept our own 
> standards as
> valid.

Do we set standards, and never change them?  If something is outside of our
standards, do we not touch it?  (ie sockets, CGI, etc.. etc..)  

See, the problem here is that the term "standards" is just too broad.  There
are some standards that are good, like using DOW instead of DOU (just
kidding!!).  But, if we set the standards to strictly and broadly then it
lets your stars go stale.  

I always think of the shop as a team.  I also believe in rewarding
excellence and eliminating mediocrity.  Now, the latter can be done one of
two ways, removing them from the team environment or making it a "standard"
to learn, test, and implement (where necessary) new standards.

Brad 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---