3 ms·

What if you just want to write software and not be responsible for mentorship? Why do capable individual contributors always have to be roped into leadership?

BurningFrog 5y ago
Work at places that don't hire junior devs.
Nbox9 5y ago
> Why do capable individual contributors always have to be roped into leadership? Training your replacement is how the cogs in the machine reproduce.
deleted 5y ago
[deleted]
indigochill 5y ago
> What if you just want to write software and not be responsible for mentorship? At a certain point, you probably know considerably more about the work than the people working around you. You might say you develop "seniority". At that point, the balance of value between your individual contributions and the knowledge you can share with others reaches a tipping point. If you're limiting the value you're bringing to the company to only individual contributions, you're capping the value you can bring the company and by correlation the compensation you're due.
pjerem 5y ago
As long as you are not your own boss (and even in this case, tbf), you are likely to not do only what you "want", because you are not the one defining what is your job. Honestly, it's a weird remark. Pretty much all jobs on this planet have aspects you wish you don't have to do. You work for your employer and your employer needs you to train the juniors. If you don't want to do that, change for an employer who only recruit senior engineers, if you can.
- thegrimmest 5y ago
  Employment is a negotiation, always has been. Senior technical staff often negotiate from a position of strength.
ljm 5y ago
I'm not sure I see mentoring as leadership as much as I see it as passing the experience along to someone less senior than you. Or did you become a capable IC in a vacuum, without the guidance of more senior engineers? Beyond that, you could go into contracting. Do the work, point to your contract whenever someone asks something else of you, move on after 3-6 months, rinse and repeat.
- thegrimmest 5y ago
  I mean, actually, mostly yes. I've usually been the last stop for technical help since school. There hasn't been anyone I can go to, so I've had to figure everything out on my own. I guess I'm wanting to work with senior peers more so than constantly dealing with juniors who seem to get lazy because they know I can solve their problems for them, often trivially.
  - sylphaenos 5y ago
    Not wanting to help juniors so they're left to struggle the way you did seems incredibly devoid of empathy. I could describe my career the same way you have, but mentoring juniors is now my favorite part of the job. When you were a junior, would you have been satisfied regurgitating a senior's answer without understanding it, or would you have wanted to learn? If you were into learning, why assume nobody else will be? When pairing with juniors, I avoid directly solving problems for them as much as possible–lessons tend to stick better when you ask leading questions and let them discover solutions for themselves. Perhaps this technique would also work to filter out "lazy" questions. Working with a mix of super competent developers at all levels has really driven home for me that everyone is better at something, and worse at something, than you are. I've learned lots of new things from developers with less experience than me. I've also worked with many devs with senior titles who were worse off than most juniors. Ultimately it's okay to find mentoring unenjoyable, but if this describes you, please stick to teams with most/all seniors and don't agree to mentor even if pressured. Attitudes like this can really exacerbate imposter syndrome for juniors, and I've seen it damage several careers.
    - 5y ago
forty 5y ago
I think there is a limit of the efficiency of a single person. At some point, helping out others to be more efficient is more efficient than doing it all by yourself. With that said, I don't see anything wrong with stagnating at your peak IC efficiency if that's what makes you happy. I agree with sibling which says that mentoring is not leadership. Helping out others is not the same as giving them instructions or evaluating performances for example. However I can understand that someone would like none of that.

BurningFrog 5y ago

Work at places that don't hire junior devs.

Nbox9 5y ago

> Why do capable individual contributors always have to be roped into leadership? Training your replacement is how the cogs in the machine reproduce.

deleted 5y ago

[deleted]

indigochill 5y ago

> What if you just want to write software and not be responsible for mentorship? At a certain point, you probably know considerably more about the work than the people working around you. You might say you develop "seniority". At that point, the balance of value between your individual contributions and the knowledge you can share with others reaches a tipping point. If you're limiting the value you're bringing to the company to only individual contributions, you're capping the value you can bring the company and by correlation the compensation you're due.

pjerem 5y ago

As long as you are not your own boss (and even in this case, tbf), you are likely to not do only what you "want", because you are not the one defining what is your job. Honestly, it's a weird remark. Pretty much all jobs on this planet have aspects you wish you don't have to do. You work for your employer and your employer needs you to train the juniors. If you don't want to do that, change for an employer who only recruit senior engineers, if you can.

thegrimmest 5y ago
Employment is a negotiation, always has been. Senior technical staff often negotiate from a position of strength.

ljm 5y ago

I'm not sure I see mentoring as leadership as much as I see it as passing the experience along to someone less senior than you. Or did you become a capable IC in a vacuum, without the guidance of more senior engineers? Beyond that, you could go into contracting. Do the work, point to your contract whenever someone asks something else of you, move on after 3-6 months, rinse and repeat.

thegrimmest 5y ago
I mean, actually, mostly yes. I've usually been the last stop for technical help since school. There hasn't been anyone I can go to, so I've had to figure everything out on my own. I guess I'm wanting to work with senior peers more so than constantly dealing with juniors who seem to get lazy because they know I can solve their problems for them, often trivially.
- sylphaenos 5y ago
  Not wanting to help juniors so they're left to struggle the way you did seems incredibly devoid of empathy. I could describe my career the same way you have, but mentoring juniors is now my favorite part of the job. When you were a junior, would you have been satisfied regurgitating a senior's answer without understanding it, or would you have wanted to learn? If you were into learning, why assume nobody else will be? When pairing with juniors, I avoid directly solving problems for them as much as possible–lessons tend to stick better when you ask leading questions and let them discover solutions for themselves. Perhaps this technique would also work to filter out "lazy" questions. Working with a mix of super competent developers at all levels has really driven home for me that everyone is better at something, and worse at something, than you are. I've learned lots of new things from developers with less experience than me. I've also worked with many devs with senior titles who were worse off than most juniors. Ultimately it's okay to find mentoring unenjoyable, but if this describes you, please stick to teams with most/all seniors and don't agree to mentor even if pressured. Attitudes like this can really exacerbate imposter syndrome for juniors, and I've seen it damage several careers.
  - 5y ago

forty 5y ago

I think there is a limit of the efficiency of a single person. At some point, helping out others to be more efficient is more efficient than doing it all by yourself. With that said, I don't see anything wrong with stagnating at your peak IC efficiency if that's what makes you happy. I agree with sibling which says that mentoring is not leadership. Helping out others is not the same as giving them instructions or evaluating performances for example. However I can understand that someone would like none of that.