This is funny because the same exact joke could be made about software engineers due to them not having a professional certification like electrical, civil, etc.
That's where I thought the joke was going when I first read it.
There is PE licensing for software engineers though?
As of 2013 I believe, but it was discontinued in 2019. Fairly rare to see in the wild outside of specific domains like medical device coding or other areas where failure isn't acceptable.
what’s a bootcamp engineer?
I think it's a joke for the people who pay into those 6-month software engineering bootcamps.
Ehh, if someone can make more than me by doing a 6 month course, I say good for them.
Sure, I'm likely to have a deeper understanding with my 4 year degree, but like... the more that person gets paid, the easier it is for me to negotiate my own salary.
I'll never call for anyone to have their wage cut just to make myself feel smug. I see this all the time in the minimum wage "debate," and it drives me nuts.
Don't let him in the club.
Undersigned, Prompt Engineer.
I'm not against bootcamps, but there are so many caveats.
-
Most bootcamp instructors have no business teaching. They have no qualifications for it, and rarely have the experience to teach the subject matter.
-
Many bootcamps are owned by agencies or companies looking for cheap labour, with many making false promises on employment - because they give them a temporary contract to get cheap devs. It was painful to see so many bootcamp grads last year, entering an empty market.
-
They are often very expensive, to the point where I've worked with people woefully unqualified, who put up with so much shit because they're in debt. They were promised a career, only to be taught just enough to do basic tasks in React, and then being limited in what they can do.
-
You end up with a horrendous amount of imposter syndrome, in an industry where people already feel like frauds.
-
I'm in the UK, and you wouldn't believe how many people go to bootcamps and assume we're all making £100k salaries. Hell, where I live, I regularly get roles for senior engineers that are £40k a year. A woman I used to work with gave up her £30k a year job to be a front-end developer for £20k, with zero benefits, no union, etc.
My bootcamp had pretty great instructors, but also a focus on learning how to teach yourself. It was a bit longer than some because it was full stack. I think it's like university, you get out what you put in. Some folks got nothing from it, I did great. Got my first job for 70k the same week I left. 5 years later I'm making over 160k.
-
Bootcamp® -> Audio Engineer, perhaps?
Maybe for those audio engineerings who end up on the mastering side of things but those who go down the live sound systems engineer path definitely deserves the same level of respect as any other engineering profession.
Computer science is not engineering. Neither is software engineering.
CS isn't, but software engineering takes strict approaches to design and development for safety critical systems. I'm not talking about finance applications however.
I'm talking about like flight control computers, valve assist device controllers, medical lab automation and notification systems, weapon platform communication systems.
You do have stamping engineers for telecom design. As far as I know that's the only real engineering title from the perspective that the sign off of the work carries well defined legal liability. I was director of engineering for a large org and the only stamping engineers in the org were telecom designers, not the security, software, systems, cloud, network, etc folks. Nothing against then either, but historically engineer meant something very specific prior to the rise of information technology.
Edit: actually in 2013 NCEES added a PE cert for software engineering, but it was discontinued on 2019.
Professional engineering is really about implementing processes and procedures that create reliable and dependable systems. Ultimately it's about responsibility and risk management. Being an engineer has nothing to do with understanding or implementing technology or technical details and specifications (unless you are in an extremely junior level engineering position). That work already has another title: that's called being a technologist (and there ain't nothing wrong with that title and that work).
Very, very, very few technologists (including self-taught programmers, computer scientists, and even some engineering grads) have, or even understand the skills needed to manage technical risk, simply because those skills are not part of any of those curriculums and the licensure required to be recognized to conduct those activities. It requires knowledge, training, and certification specifically, not just a university degree or x years on the job. Of course, it's not the sort of distinction that the general public understands by "engineering" since the public kind of just takes the act of technical risk management for granted.
Conversely, it's perhaps also why the number of engineers with hands-on skills is shockingly lower than we expect: using technology is not on the engineering curriculum.
But yeah, just because the general public confuses technical skills with engineering doesn't give you, lacking all three of : an accredited engineering degree, an engineering licence, and perhaps most importantly, malpractice insurance, licence to call yourself an engineer.
What are you talking about? I am pretty confused by your entire perspective How is using technology not in the engineering curriculum? Building robots and programming was at least half of my degree. And risk management is a very, very, small part of it, just a couple factors you add to some calculations basically.
engineer UK /ˌen.dʒɪˈnɪər/ US /ˌen.dʒɪˈnɪr/
a person whose job is to design or build machines, engines, or electrical equipment, or things such as roads, railways, or bridges, using scientific principles:
-
a civil engineer
-
a mechanical/structural engineer
-
a software engineer
I'm all for letting people ramble, but Engineering is, by definition, the design of tecnical stuff.
Risk management is a part of "designing things", but it is not what makes you an engineer. Converting technology into objects that solve problems is what makes you an engineer.
And there are lots of disciplines out there that started calling themselves engineers while they are objectively very deep into the grey area. If your work does not involve calculus, logic or physics of some kind, it is highly likely that you are not in fact a real engineer. (Looking at you, Sales and Marketing Engineers)
-
Because they are referring to engineering disciplines that predate all of the stuff you mention. When mechanical, structural, civic, etc engineers sign off on a design (stamp it) the incur personal liability if there is a defect in the design that kills someone or causes damage. There are certifications for telecom design and processes that require them to stamp designs, but otherwise most of what is lumped together as technology doesn't constitute engineering from a legal or historical perspective. However the titles sort of took off and created two sets of meanings.
If software engineering was treated as engineering in the way that mechanical or others forms are, you would get a degree, get an entry level job at a firm as a junior, and after a few years, study and get certified to stamp designs/code systems, etc.
Now, outside of places like code for flight systems, medical devices, power plants, etc there isn't a need for that kind of rigor, but those are the areas that would require licensing if it was available.
Not following this one. Are we talking about dual booting or is this some military thing that I’m too non-combatant to understand?
That would be a combat engineer
Neither. Software engineer are not true engineers in a sense that they don't require a certification. So it's just a title. Most boot camps are for full stack, but I guess some are software engineer boot camps. That or the fact that they get a job as such title with only a boot camp.
Of course you're an engineer. I could tell you didn't have to take gen ed courses from the punctuation mistake.
The boot camp morons usually don't make it past six months in my experience
