I became a team/technical lead because I love making technical teams kick-ass :-). I'm a big believer in the power of technical teams/communities to make a lot of positive change in the world.
Did you have a waning desire to write
code but still a strong desire to
I still have a strong desire to write code and build useful stuff, but I'm equally (if not more so) driven to try and have a positive effect on a team of people that build software. I try to focus on removing all of the barriers to them getting on and designing and writing great code.
Did you realise that you were more of
a people person and you could utilise
your communication skills better?
I very much enjoy the social part of my work yes, I believe that software development is at its heart a social activity as well as a technical/engineering one.
Was it because you were asked by
management and thought why not?
The very first time I was a technical lead - yes. At that time it was simply because I was the only one who knew the technology at hand (Web based Java stuff).
For the money?
Nope - for me I'd have earned more per day or per hour as a straight developer. Team/Technical leads do tend to have to put in longer hours. YMMV on this.
How were the initial few months after
making the move?
A balancing act! The politics and 'soft skill' stuff was definitely the hardest. Technical decisions etc were easier, but you get very little time to actually code until you are more experienced at managing your time.
Were relations with colleagues affected?
Initially yes - I was much younger than the rest of the team - it was a delicate balancing act of learning the art of software development from them as well as leading from the 'new technology' front.