I disagree here, and I think this is the main reason we're having this conversation. If someone has been trained up or learned on the job such that their skills are more valuable, then their employer should treat them as such and give them a raise. I've seen time and time again that good employees leave just to get compensated fairly. Alternatively people get disgruntled and leave when an experienced outside hire is brought in at a higher pay band to struggle to do the same work that they've spent years learning to do.
Small, not tech heavy companies like simple webshops, small crowdfunding platforms, etc will need someone, ANYONE, to keep working on their giant stack of legacy PHP/Rails/whatever code. The business does not support hiring very senior people and the founders are not technical at all so they don't recognize the troubles inherent in hiring a full team of juniors.After a few years the business may fold, but at that point the junior devs have gained some experience and move onwards and upwards. The attitude of "We refuse to train the future employees of our competitors.", while not un-true, fails when you can't even hire seniors.
This is crazy. If the junior needs more than 1 hour a day to be net positive (= do more work in the remaining 7 hours that you would do in that lost hour) then I would say they are a lost cause.
This is also so easy to filter at the interview level - give them homework to learn some new skill, junior candidates are generally willing to spend significant time on that and it gives you much better picture of their abilities than whiteboard puzzle.
I will say that I've hired a couple of newer developers and in some cases they've moved on, but in other cases they've stayed with the company I was at when I hired them, in some cases for 3+ years. So not everyone leaves after 2 years.
I think that companies need to be really explicit about their training and goals and try to make employees happy. Yes, that bootcamp grad is going to be super happy to work for you for the first year, and grateful to have the experience. But, yes, they are going to start looking around. So plan for how to meet their needs as best you can. Some folks will simply be on the hunt for difference and comp, others will be happy to stay at the same company if you can challenge them and continue to let them grow.
> ... at the beginning of your career it's crucial for you to expose yourself to different technologies
This is one reason I feel like a small consulting shop is the best place to start a software development career. You matter (because it is a small shop) and you'll get exposure to many domains and technologies (because it is a consulting shop).
That means that the true cost of a junior candidate vs a senior candidate isn't just their 1st year salary difference on paper, you have to count in the cost of training _and_ retaining the junior hire. That doesn't necessarily mean the math doesn't work - especially if the market for senior developers is much tighter than for junior developers.
Also the idea that you'd be mentoring for 16 hours a week one-on-one seems like it is either inflated or there was a problem. Maybe the candidate was a bad hire even for a junior role, or the mentor is micromanaging, or the work product expected was never appropriate for a junior developer - but something seems off there.
First there’s a code fluency wall you have to get over.
Then there’s a tech debt/spaghetti lesson that needs to be learned (IMO this can only be learned the hard way)
I did this with 6 months working on my own stuff 12 hours/day, then 6 months working for nothing but equity in a never gonna happen startup.
Once someone is over those two walls, they can be useful to a company. Absolutely never writing greenfield stuff, but maintenance, matching style, very clear start and end type stuff for at least a year.
Before you’ve internalized code as a fluent language and developed basic code hygiene, you should not look for a development job. Even if you get one you will be an imposter.
In what other technical field are you expected, post-school (which probably hasn't taught you a ton of practical skills), to spend a year on your own making yourself employable?
The closest comparison I have is professional musician.
you’re supposed to love the language of music. If you don’t, good luck.
And very little in common with how most people treat other technical professions.
Software also sits at this technical/creative/implementation intersection where unless you're doing something very specific, you're going to need to push/pull in different directions.
A lot of software doesn't do anything exciting, standard office CRUD, dashboards, back office tools can be banged together by a single developer as long as they can connect to a database, render a UI (web/desktop) and take requirements from the business.
There's a lot of software jobs which aren't at software companies but regular businesses who just need to track something domain specific and can't afford to tender.
The reason is because — between the people with the genuine love of the field plus those drawn in by the lure of the high-end pay — there is such an oversupply.
The second part is that the trade has a bonded period. Depending on how that is written, this becomes more difficult to enforce with at will employment. It can also lead to companies taking significant advantage of their bonded juniors. I mean... if you think this is a good model, revature is out there.
The trades face the same challenge. Over the past decade, I've gotten along well enough with my HVAC guy (one-man shop who brings on a rotating cast of apprentices) to talk with him about this. He reports the same experience ("no matter how much you train them, don't seem to be able to move beyond...").
This isn't a case of "can / cannot solve problems", either. For hobbies they delve in, that cohort appears to problem solve extremely well. I suspect the challenge is finding ways to communicate a mental model of the same problem domain that "clicks" with different personalities.
The "skilled trades" with hvac, electrician, plumbing, carpentry and such where the apprenticeship is more appropriate do have that issue again.
While it is often argued and parts of it have been refuted - The Camel Has Two Humps ( http://www.eis.mdx.ac.uk/research/PhDArea/saeed/paper1.pdf ) is applicable here.
There are people, for whatever reason, can't accept a different mental model than what they've got in their head. Software development is about twisting how you think to that of how a computer works.
I've presented this very light model of "levels":
A junior follows instructions
A mid completes tasks
A senior solves problems
There are people who plateau at each level and never go beyond that for whatever reason. In many cases it is a failure of putting the proper problem solving / learning skills in place to be able to think in a way that isn't the easy way.
* How do we prevent a predatory apprenticeship?
* How do we ensure that a non-predatory apprenticeships are able to keep their staff for a long enough duration that they're not losing out?
There is a part B to the first question on preventing predatory apprenticeships. There was an anecdote told on reddit of a person who was trying to get out of tech support and so signed with Revature for becoming a software developer, went through their bootcamp and then got placed at a company. That company found that he was rather skilled at doing tech support (rather than as a junior dev) and so moved his contract over to do tech support... getting paid less than he was getting paid doing tech support prior to joining Revature. Furthermore, the locked in two year contract meant that he did tech support for two years. At the end of this, he's got two more years of tech support on his resume that paid him less than what he was making before and no additional software development accomplishments.
So yea... Predatory apprenticeships are a problem.
The way that the "stay around long enough" of old was a signing bonus. When I started in '96 with Taos ($54k/y), I got a $5k signing bonus and $1/mile moving bonus (Mapquest was a new thing - HR was amazed at how much easier that was going to make their job in calculating the moving bonus). If I left before a year was up, I'd have to pay it back.
That works reasonably well enough when salaries are about balanced overall. But it works poorly when there are some jobs that can either offer a much larger bonus or the new pay can quickly repay the bonus. If you're making $75k/y and have a $10k bonus to repay and then get a job for $150k that bonus can be repaid within a month or so (by the time accounting sends out the "pay us back" the bonus is ready to be paid back with the increase).
This year I became a co-owner of the company that worked at for the past three years. It's a small development and consulting company and we're currently struggling to find new developers. At the same time, my girlfriend is trying to get her foot into this field. Since she's interested in a completely different tech stack than what we use, hiring her through good ol' nepotism is not going to happen. This situation gives me a small glimpse into both sides of the whole equation.
Before I continue, I want to point out that no side is at fault here. It's just market forces at play.
So why don't companies want to hire newcomers? It's simple, really. It's never worth it.
Even newcomers want competitive salaries because bootcamps, popular media, etc. paint the picture of a career in software-development as being extremely well-paid and with great benefits. This picture is absolutely true -- for senior developers. Meanwhile newcomers need to be trained and built-up, often with intensive mentoring from senior staff. In general, there's nothing wrong with that. I had a great mentor and in turn I love mentoring. But once they've gained know-how and experience, they will look for a different company hoping to use their newly acquired commercial experience as leverage to get better compensation. And that's exactly what they should do! Trust no employer that talks about crap like loyalty. Leaving your first job after max 2 years is something I would recommend every new developer. It is what the legendary Andrew Hunt (author of The Pragmatic Programmer) recommends in this podcast episode. If your first employer gives you a hefty competitive raise to keep you, use it as the new base for negotiations and still try to switch because, as Hunt puts it, at the beginning of your career it's crucial for you to expose yourself to different technologies. Maybe you'll start out as a web developer only to find out after your first job switch that you're much happier in embedded systems. Switch jobs often. Forget loyalty.
But what does that mean for employers? Let me explain it with a few of our cases. In the past, we tried hiring newcomers multiple times. In the most recent case, I was the senior responsible for the new hire. I spent up to 16 hours per week on one-on-one training in the first 6 months to get them up to speed in anticipation of a big project. They left us after 14 months for a different job in the middle of said project. I do not blame them, it's the exact right thing to do. For us, this was our third failed attempt of hiring newcomers and it was frustrating and extremely costly.
Since we're a B2B company creating software for IT departments, I asked around to see how our clients approach this whole situation. And the consensus is, "We refuse to train the future employees of our competitors. Hiring newcomers is a waste of resources. Paying the premium to get senior developers is always better." Especially small IT and software departments/businesses cannot afford training people who will just ditch the place within 2 years while big players like the FAANG companies can and have their pick from the very best newcomers.
As a result, entering this field is incredibly difficult and one has to essentially hope a company is dumb or desperate enough to take the gamble of hiring someone trying to get into developing.
So how can this be fixed? Well, I don't think there's a fix. Most newcomers will never find a job and quit trying to enter this field, the lack of senior developers is going to hurt small and mid-sized companies in the long run and many of them will eventually disappear from the market as their current developers are reaching retirement and cannot be replenished. Only newcomers who give the impression that they don't need extensive training will ever have a chance to get hired. As such, my recommendation is portfolio is king.