3 ms·
> Another perspective is to consider training junior engineers to be a core job responsibility of senior engineers. This is, I believe, a major reason why soft
by TeMPOraL 4y ago
> Another perspective is to consider training junior engineers to be a core job responsibility of senior engineers.
This is, I believe, a major reason why software sucks. Just as a person becomes somewhat competent at writing software, they're told to stop the very job they're finally good at, and focus on helping juniors become... teachers for the next batch of juniors. Unless you have a point in the process at which seniors stop teaching and go back to writing code, your software ends up being written entirely by juniors, putting a cap on the quality and delivery speed of your product.
> Most engineers who complain about teaching and mentoring shouldn't be promoted to senior level in the first place; in the long run they would probably be happier and more successful as independent consultants.
Most engineers who complain about this would be even more happy and more successful as "independent consultants" with an employment contracts and a monthly salary. I.e. those engineers are just asking to be allowed to continue to do the work they're finally proficient in, under conditions they worked so far (i.e. employment contract). Instead, they're being offered a choice of pivoting to unrelated activities they're likely not good at - either teaching or managing financial risk.
- nradov 4y agoCome on, real organizations aren't asking senior engineers to spend all their time on teaching juniors. It's like 10% time on average. Growth and turnover is a fact of life for any healthy organization. Someone has to teach the juniors or else forward progress will grind to a halt. And usually the senior engineers are the only ones with the skills and knowledge necessary to do that teaching, even if they don't particularly enjoy it and it impacts their other work.