TenCommandmentsofEgolessProgramming

I just found this link

"Ten Commandments of Egoless Programming" June 6, 2002 Lamont Adams

http://builder.com.com/5102-6404-1045782.html

KenEstes 2005.07.25

Great stuff, Ken. Thanks for the tip. - JerryWeinberg 2005.07.25

Much more even-handed that I expected given the word "Commandments" in the title. We're 9 for 10 on those where I'm working now. --DaveSmith 2005.07.26

Good for your team, Dave. 9 out of 10 is pretty good even for the original Decalog. - JerryWeinberg 2005.07.26

Don't rewrite code without consultation is the one that we miss on, because we have collective code ownership. We do occassionally consult with old-timers if we need to change really old code, but everything else is fair game. We trust one another enough that it isn't an issue. This is my first direct experience with this level of trust combined with collective code ownership, and it is simply amazing. --DaveSmith 2005.07.26

Substitute 'work product' for 'code', and the article generalizes to cover quite a wider range of team-based activities. --DaveSmith

Updated: Wednesday, July 27, 2005