I was looking on the web for new material for my OSLab programming course, when I found this very well-written collection of rules for writing nice code:
Listen what they say about leadership:
I wish i had said this, but it was said by firstname.lastname@example.org in comp.software-eng.
- lead by example
- don’t ask anything of anyone they wouldn’t do themselves
- are called on to make difficult and unpopular decisions
- keep the team focused
- reward/support their team in whatever they do
- keep/clear unnecessary crap out of the way of the team
Consensus is great. If it lasts for the project lifecycle, consider yourself blessed. I’ve been on a couple projects where two engineers just blantantly disagreed! They were always: Programmer #1 says ” x = 1″
Programmer #2 says ” x != 1″
That’s when a Project Leader is required. Unless you want to flip a coin.
Oh yah – one more thing. Project leaders: TAKE the blame when things go wrong and SHARE the credit when things go right.
Ain’t easy – but it’s the way I try to run my life.
Needless to say, I agree with all my heart, and that’s exactly how I want to be.