> we don’t hire junior developers because we can’t afford to have our senior developers mentor them. That feels too dumb to be real (which is exactly why it's probably a real thing). You don't hire senior devs to code - good junior devs can code not only "just as fast", but probably faster too! You hire senior devs to guide you WHAT and HOW to code. And they can do that so much more effectively if they don't have to…
> good junior devs can code not only "just as fast", but probably faster too! Pfft. I'm about as "senior" as it gets and I'm generally the fastest developer in any team I'm on. I've never met a junior dev that could hold a candle to me, and most senior devs I know are the same...we're coding monsters.
Who Killed the Junior Developer?
361–370 of 803 posts
Re: Who Killed the Junior Developer?
#362Those who thought it a good idea to promote people to senior level after 6 months or a year.
Re: Who Killed the Junior Developer?
#363Earlier quoted context omitted.
In my current job, for a tech company with less than 12 people, at least 5 are interns. Two of them were recent hires (January) and before they were onboarded, i had a meeting with my boss and the other senior developer regarding the new interns and my boss stated he didn’t want me and other senior dev spending too much time mentoring the interns and that if they couldn’t manage by themselves, he would just let them…
The Netherlands is a special place in Software Hell. Where the non-suits are only a cost. "Devs can't be cheap enough! We can't find decent devs!"
If you want to get paid a lot more and you have the right skills the City or Silicon Valley are good options (assuming you are allowed to move there).
Re: Who Killed the Junior Developer?
#364Reason is software is always an ancillary concern to the business. You see this in other fields, like say accounting, but the difference is that accountants leave school fully capable of employment. HR understands how to hire and manage accountants.
But programming is this black box in the corporate world that no one knows how to understand, value, or hire for. This is why every company wants rockstars, they're hoping that someone whose at least confident to present themselves as a rockstar won't be a net negative to the company.
Eventually they'll figure it out, took them a decade to figure out how to manage IT. Then companies will learn that they can't skimp on middle management for software developers. Some companies will need to give software a legit seat at the table and hire upper management. The political cover will allow shops to stabilize and with stabilization, you'll finally start seeing small and midsize organizations open up positions for juniors.
But it'll never happen so long as companies don't take software development seriously by giving them political cover. If you are a software developer nearing the middle or end of your career, you're pulling the ladder up behind you if you don't seriously consider moving into management. It's too important a job to ignore to go chase your dreams.
Re: Who Killed the Junior Developer?
#365Earlier quoted context omitted.
It's a bit of a chicken or the egg problem. Why stay at a company that doesn't invest in you?
Most developers doing the one year stint thing don't care about anything other than salary. No matter what you do for them they will jump after a year. Seeing that pattern on a resume a big warning sign. These people are simply mercenary and deserve to be treated as such.
You get maybe 25 years to make all the money you're ever really going to make as a developer. That's it! So you better fucking be a mercenary. What you're really saying when you see that on a resume is: "Here's someone I can't exploit, mistreat, or fuck over" and that terrifies you.
I'll change jobs whenever and however it suits me. Hell, I once quit a gig because the bathrooms stank too much!
Re: Who Killed the Junior Developer?
#366- you don't need a senior developer for your needs
- you can't fork out for a senior developer
- you could really use a senior developer, but won't fork out for a senior developer because your penny wise and pound foolish
- you don't understand the difference between a junior and a senior developer
- there is a labor shortage in software development and all you can hire are junior developers
Re: Who Killed the Junior Developer?
#367Earlier quoted context omitted.
> good junior devs can code not only "just as fast", but probably faster too! Pfft. I'm about as "senior" as it gets and I'm generally the fastest developer in any team I'm on. I've never met a junior dev that could hold a candle to me, and most senior devs I know are the same...we're coding monsters.
Dunning-Kruger called, they want their overblown ego steamroller back.
Re: Who Killed the Junior Developer?
#368Re: Who Killed the Junior Developer?
#369I’m the cofounder of a YC-backed Computer Science academy ( https://LambdaSchool.com/computer-science ), and we’ve noticed a few things: 1. The junior dev market is flooded. It’s also flooded with people that cannot code. We’ve done quite a bit of analysis, and we’re talking 10% can write fizzbuzz. Bootcamps are pumping people out as fast as they can collect money, and while some are solid juniors many are just compl…
> All that said, we take it for granted that we’re in an industry where people go from cold start to 6 figure salaries in 3-6 months. I’ve not aware of that ever having happened in the history of the world. There have been plenty of trained or semi-trained labour shortages in the history of the world, with similar results.
Re: Who Killed the Junior Developer?
#370> we don’t hire junior developers because we can’t afford to have our senior developers mentor them. That feels too dumb to be real (which is exactly why it's probably a real thing). You don't hire senior devs to code - good junior devs can code not only "just as fast", but probably faster too! You hire senior devs to guide you WHAT and HOW to code. And they can do that so much more effectively if they don't have to…
The problem I've seen with mentoring, in practice, is the 1 in 3 juniors that takes up all the time. Maybe the particular job doesn't suit them. Maybe they shouldn't be a dev. Maybe it's personality. Some managers, mentors or such seem to deal with this well. But, in the cases that I've seen having an employee that is not producing value is stressful and time consuming. Largely, it's driven by empathy. You don't want…
In one case you've hired someone who isn't ready to do the tasks you need without excessive scaffolding. In the other you're not providing enough structure and scaffolding for the intern to succeed with help.
Mentoring, particularly in the legal context of what makes an intern, an intern and not a Jr. Developer ought to be a short run project, and frankly if you can't commit time to providing an educational experience you shouldn't be filling your staffing needs with an intern at all.