4 ms·

Yep, can attest to this. One of the reasons why senior people are extremely productive & valuable is that they seem to know the landscape more than others, and

Yep, can attest to this. One of the reasons why senior people are extremely productive & valuable is that they seem to know the landscape more than others, and therefore know who to talk to & where to look. Half-jokingly, as soon as an "individual contributor" knows enough to be productive, they're promoted to management.

csydas 8y ago
WRT the half-joke, this is one of those truisms that probably has a lot of basis in reality, but there needs to be a corollary about the choice of the individual as well. I was heavily invested in our public facing technical side, working a lot with our on-boarding, teaching newbies to be really self-sufficient, working through the technical issues with our clients directly, and then I was asked to take on a Management position. I liked the pay raise, but I made it clear exactly what I wanted from the position, and though we butt heads on it still, my boss respects the fact that I still am heavily invested with our technical team while doing the Managerial work. We had to revisit the job definition a few times to find a description that matched what I was (am) doing and also made HR happy, but we did it. The point is that in some cases at least, a promotion to management doesn't have to be a death knell for "individual contributors". It depends on the company's willingness to accommodate the wants of the individual, and the individual's own desire to continue contributing. I know too many people who did get the Management golden ticket and relished it for just being an excuse to boss people around and make more dashboards in our CRM.
- opportune 8y ago
  At the same time, I have read from people making the transition from IC to manager that it's a mistake to hold on to your technical work. Surely this will vary from person to person, company to company, and team to team, but I find it hard to believe that people with 10-15+ years of professional dev experience are best utilizing their skills sitting far away from the code; at the same time, they can't get too focused on it and ignore their management responsibilities. I wonder how much of it has to do with team sizes. I feel like a 4 person team (inclusive) would be ideal for a manager who also wanted to act as a technical lead and contribute a moderate amount. Any bigger, and the scope of what your team does, as well as the amount of time needed to devote enough time to all your employees, starts to get too big for you to contribute at a technical (e.g. source code) level. Yet we continue to take great technical workers and put them in this weird PM-hiring-HR-architect mixture of a position where they barely continue to leverage their skills anyway

csydas 8y ago

WRT the half-joke, this is one of those truisms that probably has a lot of basis in reality, but there needs to be a corollary about the choice of the individual as well. I was heavily invested in our public facing technical side, working a lot with our on-boarding, teaching newbies to be really self-sufficient, working through the technical issues with our clients directly, and then I was asked to take on a Management position. I liked the pay raise, but I made it clear exactly what I wanted from the position, and though we butt heads on it still, my boss respects the fact that I still am heavily invested with our technical team while doing the Managerial work. We had to revisit the job definition a few times to find a description that matched what I was (am) doing and also made HR happy, but we did it. The point is that in some cases at least, a promotion to management doesn't have to be a death knell for "individual contributors". It depends on the company's willingness to accommodate the wants of the individual, and the individual's own desire to continue contributing. I know too many people who did get the Management golden ticket and relished it for just being an excuse to boss people around and make more dashboards in our CRM.

opportune 8y ago
At the same time, I have read from people making the transition from IC to manager that it's a mistake to hold on to your technical work. Surely this will vary from person to person, company to company, and team to team, but I find it hard to believe that people with 10-15+ years of professional dev experience are best utilizing their skills sitting far away from the code; at the same time, they can't get too focused on it and ignore their management responsibilities. I wonder how much of it has to do with team sizes. I feel like a 4 person team (inclusive) would be ideal for a manager who also wanted to act as a technical lead and contribute a moderate amount. Any bigger, and the scope of what your team does, as well as the amount of time needed to devote enough time to all your employees, starts to get too big for you to contribute at a technical (e.g. source code) level. Yet we continue to take great technical workers and put them in this weird PM-hiring-HR-architect mixture of a position where they barely continue to leverage their skills anyway