This is a good opportunity for somebody.
I think the situation we're in is an uncomfortable one. Basically, the tech world needs people, and the four-year approach seems too slow. Sadly, nothing I've seen - and I've been affiliated with a bootcamp - seems to both provide the people required and give them the grounding for a career.
We as an industry have this burning need to believe that there must be something better. However, I submit that this is the equivalent of protesting "There must be a better way!" when confronted with an uncomfortable policy decision. In both cases the sentiment is laudable, but fails to conjure the alternative into being.
It is a good opportunity for somebody. As near as I can tell, that somebody is the four-year CS programs of the world.
The only alternative I can see is bifurcating development work into high-skill people who know CS and low-skill code monkeys. I'm uncomfortable with this, but I suppose it could be workable. We'd just have to disabuse all those code monkeys of the illusion that they're going to become computer scientists.
These apprenticeships are for like $500/week. That's not a good opportunity for some in a four-year CS program.
I'm saying that the alternative models proposed are even worse fits for the problem than the model considered lacking. This isn't a field currently structured for a relatively short training period to lead to a typical career.
Maybe medicine should be the goal model. Doctors and nurses, code monkeys and software engineers.
You don't need to relearn imaginary numbers or assembly programming to be a good software developer.
You could start them with a job. They'd have, by their standards, a great job. What they almost certainly wouldn't have is a typical career in software engineering following that job and the obsolescence of their skillset.
But for most of the programmers I know, they're just writing code that runs a business which is certainly not IT.
Current technologies do not move fast, because computer science and maths in general are still hard.
This year's "hot" approach isn't fundamentally different from last year's hot approach, and it won't be fundamentally different from next year's hot approach.
Our educational system needs to be designed around enabling people to understand the fundamentals of what they're doing, instead of code-by-marketing. Those fundamentals do not change rapidly; the books have a lifetime measured in decades, not days, and they provide the background necessary to evaluate, understand, implement, or reject any of those "hot" new approaches.
I think we're in violent agreement. If you know your CS and mathematics, the current hotness is stuff you can grasp. If you don't, odds are you're in trouble.
Yes, technology moves fast and if one wants to stay current in the field, one has to keep learning.
But the fundamentals remain the same. It has been forty years since TAoCP was published for the first time. Has it become irrelevant? Hell, no. Has logic or maths changed because of this year's fad? Of course not.
Is four years a long time? Not if you want to give a young person a thorough education and a solid understanding of the craft, from the foundations up.
Instead, you know, of just train them to hammer out code in the currently most hyped language, without really knowing what they are doing and why it all works.
Teach concepts, not implementations.
Edit: Typo, standpoint clarification.
I guess I'm biased here; I grew up in Switzerland and did an apprenticeship in IT. Also, the company I've been working for the last five years has had apprentices since it's very beginnings and most of the apprentices chose to stay afterwards.
That is what I am saying is a poor fit. None of the items on this list, last I looked, are four-year apprenticeships that include CS fundamentals.
Most IT jobs start after the level of an apprentice.
Its more the perception that you will give others that "professional" software development is a lesser profession.
The other professions call this CPD imagine a junior doctor being told now you have your md your going to be doing an aprentiship the AMA would go nuts!
This was about 10 years ago and I don't know how much has changed since. I do like the system, but looking back the first thing I would change is getting rid of all the vendor/Microsoft specific courses and add stuff like algorithm design and analysis, data structures etc. Also some international recognition of the degree would be a nice to have:)
These "apprenticeships" are little better than bootcamps. They skip all the fundamentals in favor of whatever the language du jour is.
Oddly enough, the changes you suggest would bring your apprenticeship roughly in line with the four-year Bachelor's program I did here in the US. Perhaps this isn't a coincidence.
Yes my suggested changes would bring it roughly in line with a Bachelor but while working in an actual company and earning money.
To be able to take this decision seriously, you have to understand the big picture, which doesn't change fast.
Coming from a vocational bg the idea was you took kids at 14/15/16 they then did a craft apprenticeship for say 4/5 years - spending the first year fileing and fetching tea
Then if you where intelligent you did the technician level course which took another 4 years
However, I don't think apprenticeships are a good fit. The apprenticeship model is great for skills that do not change rapidly or need frequent updating. Carpentry five years ago is much the same as carpentry today. This works well because in such areas, you can afford to gloss over or just skip many fundamentals because the hands-on skills are all that will be needed for a multi-decade career.
This model doesn't map well to development. Current technologies move fast. Adapt rapidly. One year's hot approach is the next's old broken crap. Our educational systems need to be designed around enabling people to adapt rapidly. The only way I know to do this is to teach people the fundamentals they need to adapt to anything within their field.
I'm happy to entertain other approaches, but this seems like hammering a round peg into a square hole because using a square peg is inconvenient.