The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I totally agree that CP isn't manager-centric, but this is kinda my online crew. My virtual peeps. It's just my go-to for tech questions, including this one. And while I do agree with stifling creativity in this role, I know the guys here will want me to code some. So I hope I don't lose that side, but I gotta give this a go man ya know.
Not so much advice but just to recant my own experiences. I too was once a Development Manager. I didn't directly apply for the role, it was gradually assigned to me as I was the most senior developer in my team at the time (this was around 5 years ago).
So I gradually evolved from a Senior Software Developer into a Software Manager. And I didn't like it one bit. My passion is developing software. It's what gets me excited and puts a bounce in my step in the mornings.
Slowly over time the mind crushing tedium of the role got to me. I spent less and less time doing what I loved and more and more time spent in meetings, putting together the annual budget plans, drafting the development strategy and roadmap, representing and defending the team to people who's sole objective was to blame my team for why their own team had failed.
I learnt a lot about the management side of software, but that's about it. I didn't particularly enjoy my tenure as a manager, and I left after a couple of years to get back into developing software.
Life is short. Spend it doing something you love.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
I know for me my idea of what's fun has changed in the recent years, and I don't code as much at home as I used to. So as I change, I suppose the career should change with me ya know. Thanks for this, and I agree do what you love.
A few years back I wrote The Zigzag Career[^] in respoonse to Udi's article[^]. In rereading both I think the bottom-line advise still holds true: make this type of decision with your eyes open and treat it like a real career change.
Personally, I've been back and forth between manager and IC roles but have always gravitated back to the technical side. That's just me though. I didn't even find the "architecture" role that appealing. I like to build things.
Try it. You may (or may not) like it. Either way you'll end up better off (IMO).
Whatever Marc said is very true.. Never try to hog the limelight and never dictate !
And if I may add:
Never try to micro-manage - give them space to maneuver.
don't give solution immediately (specially to technical problem) even if you have one unless extremely critical time-crunch. Give pointer and let them fail and learn, That gives them great pleasure and satisfaction when they solve the problem
Advice ? The only thing I can say is that if you are going to become the manager of your current peers, that is always going to have some sticky aspects, always likely to precipitate some psychodramas.
«There is a spectrum, from "clearly desirable behaviour," to "possibly dodgy behavior that still makes some sense," to "clearly undesirable behavior." We try to make the latter into warnings or, better, errors. But stuff that is in the middle category you don’t want to restrict unless there is a clear way to work around it.» Eric Lippert, May 14, 2008