1. if you've ever made the transition from primarily coding to managing, what do you wish you had known when you started? what were your biggest questions when you started the job?
2. as developers, what are the top two or three things you wish new managers could be taught (be nice, now)?
OK, that's three questions. thanks in advance. Joe
Give them the highest salary you think is reasonable and no benefits. No 401K match, no health insurance, no company presents like ipads or what have you.
Here is why:
We pay pretty well but it is spread out over all of the above. You might have a base salary of $150K but then we pay for 100% of your $35K/year health insurance with a top rated PPO (that's for a family of 4, we cover everyone 100%), we throw another $33K into your 401K, and we bonus you another $45K.
Total comp: $266K. What the engineer will think he makes: $150K.
If I wanted to maximize profits, rather than look out for the best interests of my people, I could pay that engineer $200K (with no benefits) and he would think he makes more. Most people seem to be like that, the year end stuff doesn't count when they think about how much they make.
When I talk with our techs about their tasks and work loads, ALWAYS say what do you need from me. I make it clear that I expect the deliverable to be done right and on time. It is their responsibility to speak out and say I am having problems with X, or I am unable to complete Y because of Z. A managers job is to get your employee's the resources they need, or to find a suitable alternative if that's not possible. My job is NOT to jump in the trenches and start coding unless its to prevent the companies certain demise or to save my employee's sanity during an unexpected surge of work.
This was my hardest challenge when a manager, and in hind sight, what I wish past managers would have known. My best manager knew this and is where I learned this from.
I worked with a guy who got promoted to manager at Sun and the first thing he did (while we were all laughing at the idea of the idea of him as a manager) was to walk into our office and say "Hey, dude, you are working for me now. It's gonna be fun. What stuff do you need to get more shit done, I'll get you that."
We all stopped laughing because we all needed stuff. He got us that stuff. Great guy.
2) In dealing with individuals Competencies & Skills, wish I found the FYI Book much earlier: http://www.amazon.com/gp/product/0974589233/ref=x_gr_w_bb?ie...
I was always wondering
1) What exactly I should be doing while development is happening? (Hint: QA/generating issue-reports) And am I micromanaging too much?
I'm definitely a Maker type of person (I score 22% Fast / 78% Slow on this Pace Indicator I use [1], which is similar) so a mid-afternoon team meeting can ruin my day.
A good manager can step away from their team for a few days without things falling apart.
The hardest thing to learn is to address problems early - nip it in the bud. Learn to delegate and plan for / foresee future problems before they impact your team.
"If someone does a job 70% as well as you would do it yourself, you should approve their work."
It's sometimes referred to as the 70% rule.
I'd recommend treating it as such.