It's the same thing for software development. You can learn how to be useful or productive (albeit with a limited set of skills) in several months of applied training. That doesn't mean you're automatically skilled in things such as handling big data, compiler construction, HPC/optimization, systems programming, multithreaded applications...the list goes on.
However, as far as I can tell, not only is a 4 year program overkill for what most people want to do, a CS bachelor's degree usually doesn't cover particularly relevant information. A computer science degree teaches computer science, not software engineering. It's intended to introduce basic concepts which will be needed when proceeding on to do research.
What most people really want is an education in software engineering.
That said, I completely agree with your sentiment: Had my priority been to establish a software engineering career, a whole lot of what I did could have been skipped and substituted for things like learning how to write good unit tests.
I also strongly agree with you on "finished apprenticeship" vs. "master."
On the other end of the spectrum, I know people who got a degree completed unrelated to STEM, and through some on-the-job training managed to work their way into reasonably successful careers doing routine web development, or similar things. That certainly looks more like a trade. It's a marketable, valuable skill. They had to put some effort into something like an apprenticeship. But it's not exactly half their life training for a formal engineering discipline either.
There are plenty of respectable ways to make a living in the software world that don't require a 4-year degree from en engineering school. I don't think we should pretend otherwise or force people into the way we got our education. I'm more on the engineering side, but I'm very passionate about my work, and not everyone needs to be like that. Some people just want to make a living and focus on other things in life.
In Germany, there are two different flavors for the apprenticeship to "Fachinformatiker" (Computer Science Expert): One for software development and one for systems integrations, there's even a sub-specialization for "support".
Not my translation, it's the "official" translation from the German Chamber of Industry and Commerce [0].
> I have no idea what the american equivalent is, because there might not be a standardized title, and maybe expert is not a protected title.
I don't think there is a US equivalent to the German "Fachinformatiker", just like there's generally no real US equivalent to the German apprenticeship system. Imho Fachinformatiker as an apprenticeship is a good approach because not every IT job needs to be on an academic level, no reason to lock a whole field of work behind the entry-barrier of having an academic title/university education.
[0] https://www.darmstadt.ihk.de/produktmarken/aus_und_weiterbil...
Is it engineering then? Or is it scientific? Because they're not the same thing.
Programmers are also not, in general, software engineers.
It's not about getting 'caught up in titles' either, IMO. It's an important distinction. Computer science programmes get flack for not teaching practical software engineering skills, which is totally unreasonable. Just as we have physics programmes, we should have proper computer science programmes.
You are allowed to do a physics degree and offer physics courses without people going 'but how do I design bridges??'. Yet every computer science lecturer will tell you they've had people ask 'but what does this have to do with making websites??'.
Your comment defines a trade skill as one "that most anyone should be able to learn in several months without a general STEM education". So, let's evaluate that question for a few different trades/professions.
"Software Engineering": We have determined, through experimental proof, that bootcamps can make (some) novice non-degree-holders into employable software engineers in 3 months. Probably 3-18 months would cover most people that would otherwise be entering college in a CS major.
At parties I like to ask people how long it would take to teach someone to do their job. (Posit that they're smart and interested.) For most white-collar jobs, people answer "6-18 months". Most trade schools are somewhere in that region as well.
In my opinion, most professions would be well-served by the bootcamp model (like software engineering is) and a 6-18 month training period. So per your definition, I would say there are few professions out there, if any.
A good rule of thumb: can they do their job if Stackoverflow.com is blocked at the corporate firewall?
Microsoft was fined but still hasn't changed their certificate titles, and this fined was levied in 2004. So it shows that enforcement of this is spotty at best.
The more I learn about serious computer science and engineering work, the more I realize that I can't do that kind of work with any degree of fluency...yet. I'm continuing to work (slowly) toward that direction. But I've also realized that relatively few software developer jobs actually require these skills.
Nonetheless, I am a very solid software developer, who can built robust, correct, and reliable software.
Actually, I think "software technician" is a great name for bootcamp graduates to hold. It perfectly captures the level of training they've finished.
Engineers or developers? How can you differentiate?
I've been writing code for about twenty-two years now (fifteen getting paid for it), I build large systems with tight fault tolerances and work to deeply understand my failure cases.
Your "6-18 months" is probably enough to make a code grinder. I wouldn't say twenty years, with current tools and current culture, has made me an engineer.
> Code grinder
Well those semantical terms won't get you anywhere. There isn't a difference which will reach consensus.
But alas, I see the root of your argument. Universities aren't teaching people to be great for corporate America, despite how warped that ideal of higher learning has become. Coding schools are sticking to what is relevant for current roles. Many of the coding schools already know what the current roles are and act as glorified recruiters making the bulk of their earnings on the placement of their students in roles they have already lined up.
Being productive in a corporate environment doesn't take much time at the right level of the stack.
I fully agree, and I think that's a great job to teach to and for people to have. I think conflating it with this-had-better-frigging-work engineering is dangerous to both the profession and the people who trust us to do good work for them (both as employers/clients and as a society).
Engineer means something. Hell, I build systems expecting them to fail and I understand how to proof them, to the best of my time/cost allowances, against failure. I'm still not "an engineer". And--and this is important--I am also not held liable like one.
If it actually meant something we wouldn't have the industry standard interview consisting of seeing if you can do basic comp sci algorithms either. As far as I am aware other engineering disciplines don't get asked to whiteboard something like calculus to see if they can do the basics when they go for a new job
And, yes, the tire fire that is interviewing is a large part of this.
A good portion of the software community does not want a governing body over the industry. If we are going to accept that, then we also need to accept that titles are meaningless because there are no standards.
But, by "muddying", I was referring to the original post I replied to that pimped services for turning people into somewhat-competent web developers and calling them engineers. Sorry for the confusion.
Exactly the same could be said about electric engineers, except that they are regulated and need to be certified.
This is not denigration. I have worked with real engineers that wrote code. Sign off on it, and I will listen.
Maybe. I'd argue if you're mostly working with frameworks, you're probably more of a technician than an engineer.
I believe software engineering is a thing, but most who carry that job title don't do it. In the same sense that there's not much "science" in computer science.
There's no need to pretend that code monkeys who churn out generic CRUD programs are highly skilled or talented. It's respectable, pays enough, demands enough, and many people are capable of it; it's as close to a blue collar office job as you could ask for.
Actual software "engineers," working on complex problems in computation, mathematics, physics, etc. are hugely outnumbered, even today, let alone tomorrow.
Yes.
Is this a profession or a trade?
Is “Software Engineering” a euphemism that exaggerates our jobs?
Did I waste my time getting a CS degree and spending half my life learning to do this?
I’m all in favor of anyone who wants to learn programming having a go at it, but I hope it doesn’t make me an elitist if I wonder whether it’s fair to consider software dev or engineering a trade skill that most anyone should be able to learn in several months without a general STEM education...