3 ms·
Companies have woken up to the fact that for the most part people no longer stay in one job for more than a few years. Training junior people makes sense econo
by cimmanom 9y ago
Companies have woken up to the fact that for the most part people no longer stay in one job for more than a few years.
Training junior people makes sense economically only if they get up to speed and positive productivity within a small fraction of the time they'll be with your company.
Since a bad developer creates enormous negative productivity, it can be years before a new programmer's contributions are productive at all, let alone greater than the ongoing opportunity cost of the time spent mentoring them, let alone the sunk cost of months to years of mentorship.
This time makes sense only to invest if you expect the developer you trained to stay with you for many years. That expectation has become less and less rational over the past couple decades.
Nowadays if you take on and train a junior, you're taking the loss on that training - not to train someone who's going to be a good mid-level developer in your own company, but who's going to jump ship for somewhere else well before you can make back the senior developer time spent on them.
- mratzloff 9y agoYou shouldn't have this problem if you 1) hire for intelligence, drive, cooperation, and passion about the mission or opportunity, 2) give them continual opportunities to grow and take on increasing responsibility, and 3) compensate them appropriately (as a manager, privately reevalute title and comp every three months for the first year). Of course, these are the same things (among others) that are true for every engineer. There's an endless supply of juniors to choose from, so there's no excuse for a bad hire. If they leave for more money that you could have paid them, that's on you, too. Do those things and you'll win their loyalty.