Sat 26 Aug 2006
I would be the first to admit it. I’m a geek. I love technology. I think well written software is an absolute thing of beauty. There is no better feeling than being a member of team (coding solo is not really my bag) that cuts quality code that can be adapted to meet future (read as unplanned) requirements. That simply rocks my world.
That said, these days I’ve found hidden value in not being a part of the coding team - the engine. I’m no longer a part of the engine but more the oil in the engine. Basically, if there are guys that are better than you, the that best thing to do is let them get on with it. However, an engine needs tuning here and tweaking there to deliver the best results possible, in the shortest space of time. Every team needs oil, without it, things get stuck and engine stops performing. More to the point, you’re either oil or a part of the engine. You cannot be both, or something, somewhere will break!
So ask yourself, in your team, what are you - oil or part of the engine?
August 31st, 2006 at 1:31 pm
I’m a developer, not a lead, but I subscribe 100% to the notion of ‘kai zen’ which to me means actively looking for small changes to improve the way I and the team work. It really doesn’t take up much of my day, I feel more satified with my work, and every now and again I make a change that it’s seriously appreciated.
I think it would be unhealthy for people to see themselves as being purely “part of the engine”. There’s got to be some oil in there.
August 31st, 2006 at 1:57 pm
I think you’ve taken this a little too literally. It is not suggesting a hierachy of mega power. Maybe the metaphor needs work, maybe? But to take it even further, all engine parts come lubricated off the shelf. The team is a team is a team, but some have more time to oil than others that’s all. As you say, everyone oils.
June 27th, 2008 at 12:41 am
Valtrex….
Valtrex….