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.
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.