7 ms·
A key point that you're missing is that junior devs are likely to jump ship at least once in their career trajectory before they become senior devs. So yes, ju
by CydeWeys 9y ago
A key point that you're missing is that junior devs are likely to jump ship at least once in their career trajectory before they become senior devs. So yes, junior devs do need to be trained by someone, but if you're going to put in a lot of work and not receive much of the benefit, it's not in your best interest.
There's a variety of reasons for why devs jump ship so often (including compensation), but unless you can tackle that problem first and solve it, it doesn't make sense to jump head-first into expanded junior dev mentorship.
- Joof 9y agoYou could poach them too. It could be a tragedy of the commons scenario, but it would be nice.
- AFNobody 9y agoMarket rate compensation, non-toxic culture, and realistic expectations for work output solves 90% of the reasons reasonable people leave jobs. People claim all sorts of reasons for leaving jobs but its always one of those three or uncertainty about company longevity. (i.e. acquisition/financial difficulties for the company) The other 10% is people who are naive or have a family/relocation related issue that you can never control for. And yes, before you say it is impossible, I've worked at a company where "voluntary quits" was _that_ low and no one voluntarily left because they knew how good they had it. Literally, in a team of 20+ I knew all 3 people who voluntarily quit over the span of 10 years there.
- a_t48 9y agoComeon now, there are more reasons than that for people to leave, like a new exciting opportunity appearing.
- AFNobody 9y agoPeople _say_ that to acquaintances, to coworkers. Just like they stay positive in the workplace and a bunch of other fronts people keep up as part of work life. Your job at work is to sell yourself and your skillset. With people you talk with honestly outside of work YMMV but I've never seen that as a legitimate thing except with naive people who ended up regretting it. I've only seen people being happy with it when they were already underpaid, unhappy with the culture, or forced to work absurd hours to keep their jobs.
- marcosdumay 9y ago> a new exciting opportunity You mean a salary or title increase? Yeah, that's in the GP's comment.
- Huggernaut 9y agoNo, like a project or team you really want to work on for any number of reasons other than salary or title.
- chrismcb 9y agoWhen I first got into programming, as a high school intern in the early eighties, I was told a programmer stays at a job, on average for the years. I haven't heard this number change at all. While I'm sure there are many jobs where people stay along time, the average length of stay is still fairly short. Boredom and wanting to work on something new is probably the biggest driver
- biotech 9y agoBoredom and wanting to work on something new is probably the biggest driver I have to disagree with this point. Switching jobs is a very stressful and scary experience. Most people don't want to jeopardize their income without having some very strong motivator. In my experience, the most common reasons someone changes jobs is: - Promise of a higher income - Low perceived stability at the current job (employees want to secure a new job before they're layoffs) - Toxic work environment
- Mandatum 9y agoI HAD to switch jobs 3 times within 2 years when first starting. (Redundancy, restructure, outsourcing.) It's no longer scary or stressful. I now choose to switch jobs regularly because I get better incentives to join somewhere else and I get more bargaining power with each transition. C-levels and shareholders made it this way - if they kept with market rates and the organisation put more value in employees and their IT I'd stay around. But I've been seeing more and more of a shift to outcome-based budgeting, maintenance and refactoring isn't even part of BAU budgeting - it's strapped on to project work. This is likely exclusive to non-tech companies (even though most companies are shifting towards tech as their basis ala "Software is Eating The World"). Managers can only do so much within an org, I haven't worked for a manager I didn't like (I've turned down jobs based on my interview process though). Not US based.
- AFNobody 9y ago> When I first got into programming, as a high school intern in the early eighties, I was told a programmer stays at a job, on average for the years. I haven't heard this number change at all. While I'm sure there are many jobs where people stay along time, the average length of stay is still fairly short. I've literally worked at _one_ place that scored well on those three items. Most places are racing to the bottom in one or two of those. Usually it is pay unless you are somewhere competitive like the Bay Area. > Boredom and wanting to work on something new is probably the biggest driver That is much like the "exciting new opportunity" story people tell about why they changed jobs. It is not _real_ in the literal sense. If it was real, they would shop around internally to change projects and succeed. There would be no real need to change jobs. Idk where you have worked but I've literally never worked on the same project for longer than 1-2 years. Even if I was at the same employer for 6+. If you have people with realistic expectations who aren't piling on technical debt, maintenance work _should_ be negligible even if you are lightly attached to old projects.
- odiroot 9y agoYou may have a point in here. Provided I have productive working conditions and 5-10% YoY salary bump I'd probably never have the inertia to look for a new job myself.
- tanilama 9y agoMost company doesn't work this way. They are not really toxic, it is just their internal policy structure. Junior devs should look for jobs once they reach the 2 years mark any more, for their own good as well. They now know better what they want to do, more focused, more experienced, and most importantly, more valuable on the market.
- wlesieutre 9y agoOnce they're trained up to a point where another company is willing to pay them more for a more senior position, you could give them a raise? Congrats! You trained a junior dev and they turned into a senior dev.
- Terr_ 9y agoThat's true but it also misses the point: A portion of the limited money-pool you could have used for their raise is already gone, spend in the extra costs (direct or opportunity) of the training period. There isn't much of a "raw mercenary economics" argument for training (which the MBA types prefer), you've got to talk about intangibles like loyalty, goodwill, social connections, etc.
- crooked-v 9y agoBut if they leave, now you have to pay to train a new junior dev, and you still have to pay full price for a different senior dev.
- Declanomous 9y agoThat doesn't make sense to me. Let's say you train someone whose salary is [x]. After training, their market salary would be 30% higher; [1.3x]. Are you suggesting that if they end up with a hypothetical 10% raise, to [1.1x] because [.2x] was spent on training? That's absurd. You can't just walk out on the street and hire a person who is already trained for [1.3x]. You have to devote resources to the hiring process, which are probably nearly as expensive as training up a junior dev, all things considered. I honestly think the difference in the second example is that the expenses in the second example are paying the kinds of people who make stupid personnel decisions like this. I'm obviously cynical about the whole thing, but it seems that MBA-style thinking is almost deliberately evil. I have friends who have gotten MBAs from top schools, and friends who work in management consulting for the Big 4, and I've talked at length with them about their feelings about business practices that they implement and support. I literally have never gotten an answer that justifies philosophical objections to their work, beyond perhaps "well, it's just the way it's done." I think it's a myth that organizations have to behave in a deliberately sociopathic manner in order to be successful. I mean, to a certain extent being a sociopath is an advantage, but I really don't think that's really a necessity. On the flip side, I acknowledge that I am not very good at divorcing who I am from what I do. It's why I've made a career helping non-profits and social enterprises. I'd probably be a healthier person if I were able to get less invested in what I do.
- kokey 9y agoNot just the risk of them jumping ship, the problem is that because mid to senior dev salaries are highly desirable it attracts juniors into the field who are not suited to the job but like the idea of working in the industry or the potential money in it. So, you spend time training a group of people where some aren't suited for the job but you spend a lot of time on them and the better ones leave quickly. If you don't pick the juniors carefully in the first place and if you don't have the environment and renumeration to keep the better ones from leaving then it's probably better to just not spend too much time on recruiting them. It actually might work well for a company that doesn't want or need a large dev team. Also, not everyone is good at mentoring, some of the best people are often self taught and some of them find it difficult to teach others.
- mooreds 9y agoI did say "they still need raises" :) But I get what you are saying. As a junior dev, I have received at least one double digit percentage raise. This was a while ago, and perhaps I worked for an enlightened boss, or maybe I was just really really undermarket. But it can and should happen. The long term approach would be to give the juniors raises and challenge them and keep them within the org. Unfortunately the short term perspective doesn't value that and so jumping ship is the best way to get more money, causing the org to lose all the training and the institutional memory.
- taurath 9y agoThey jump ship more often when they stop or significantly slow growing than when for compensation, but eventually compensation becomes a problem just the same as at any job. You're underestimating how quickly a junior dev can be putting out useful work - within a few months they'll be tackling a ton of bugs and freeing up senior people to work on bigger features. Yes, eventually they leave, but it seems like everyone seems to think they're just dead weight.