The only reason we don't hear about the plumbing cartel going after the home repair business that isn't licensed for plumbing in every state it operates in but wrote "plumbing" on its vans in all states is because HN doesn't really concern itself with those sort of matters.
I wouldn't limit that statement to state-backed: it is how most (or at least many) private organizations and unions work too, from teamsters to fifa to the NRA. State backed organizations just have the extra advantage of being explicitly state backed.
I mean the board that licenses Civil Engineers, for example, should be very stringent. We don't live in buildings that aren't structurally sound or drive on half-assed bridges.
Professional Engineers hold themselves to an ethical standard that they're not even legally required to uphold, yet they still do because this organization keeps them in check.
> for me to call my self a "Professional Engineer", I have to pass a test almost wholly focused on Civil Engineering
isn't true. The FE exam has a number of discipline options, including Electrical and Computer[0] and the PE exam is then done be discipline.
[0] https://ncees.org/wp-content/uploads/FE-Electrical-and-Compu...
https://ncees.org/engineering/fe/
So I could (but almost certainly won't) take the "Industrial Engineering" exam and focus mainly on IE topics:
https://ncees.org/wp-content/uploads/FE-Industrial-and-Syste...
List of Engineering Disciplines that can take the PE exam:
- Agricultural and Biological Engineering - Architectural Engineering - Chemical - Civil - Control Systems - Electrical and Computer - Environmental - Fire Protection - Industrial and Systems - Mechanical - Metallurgical and Materials - Mining and Mineral Processing - Naval Architecture and Marine - Nuclear - Petroleum - Structural
Hydraulic engineers would probably be scratching their heads at this. The intersection between engineering and plumbing is well charted territory.
Just based on the number of idiotic major bridge designs we have had over the Mississippi river, I'm inclined to go with Marohn on this one. Kick all of the bozos more interested in politics than actual real engineering out.
That's convenient. The organizations assert that they can tell certified persons what's allowed and not, but if the certified person follows all the rules and something still goes sideways, the license ends up being worthless, because they can't say, "I did it this way because that's what the standards I'm required to adhere to say"?
As a programmer (who gets titled "software engineer" whether I liked it or not) this is terrible. What incentive would I have for getting a license if it doesn't protect me from liability?
When you give your stamp of approval on a project then you're legally liable for it.
You can be sued for incompetence. Then, you have to go to court and defend yourself. Or, more commonly, your company will send a lawyer but you still may be called to testify.
Most public works and building is template driven with standardized components. Highway bridges pretty much look the same if they were built at the same time. There’s probably 10-15 guys in the average state who periodically update the standards. 80% of the rest of the work is drudgery done by overworked, underpaid assistants and non-professional engineers, signed off on by a PE later.
What PEs do accomplish is making it outrageously expensive to perform basic public works that were accomplished successfully by a DPW guy with a paint roller 40 years ago. Painting a crosswalk and installing a traffic light costs nearly $1M, because you need to hire an engineering firm to duplicate a template, and sign off on placement of lines, etc.
But in English using the title Doctor is assumed to mean medical specialist in general circumstances. Any Ed.D that stands up when the flight attendant asks, “Is there a doctor on the plane?” deserves a scolding at the very least.
Interestingly every single American with any kind of a technical Ph.D that I’ve ever met goes by first name and doesn’t balk at being called mister in all but the most formal circumstances (Germans are an entirely different matter). It’s the ones with Ph.Ds in things like English that get demanding about being called doctor in everyday life.
Many doctors these days are women.
I dunno... Jill Biden made an ad in which she called herself by her title 'Doctor' (which is proper, since she has an EdD) and then gave advice on COVID, and we were told that this was sexist because she's really a doctor by many mainstream news outlets.
As someone that spent hundreds of thousands to get answers, and majority of my answers came from other people going through same nonsense.
For anything complicated you have to become your own doctor. Medical community is broken on all but straightforward cases.
You can't legally present yourself as a professional engineer without that license.
I will guarantee you that is not how that vast majority of the population would interpret it. Very few people even know that there is such a thing as a licensed professional engineer.
Most reasonable people would take the term "professional engineer" to mean somebody who performs engineering work of some sort in a professional capacity.
Actual doing something should take precedence over some license primary used to gatekeep a profession and fill state coffers with licensing fees.
The fact that we still have guilds operating in the 21st century is embarrassing.
I disagree.
>Very few people even know that there is such a thing as a licensed professional engineer.
>Most reasonable people would take the term "professional engineer" to mean somebody who performs engineering work of some sort in a professional capacity.
Where did you source this information?
https://www.bpelsg.ca.gov/laws/pe_act.pdf
If you don't like the law, complain to your local state legislator. For me, it didn't affect my ability to do my job or get employed, so I never cared about it. I supposed they could change the name to "licensed engineer. It doesn't bother me that the person designing roads, buildings or electrical distribution systems has to be licensed. My wife has a friend (Civil Engineer, PE) and it seems like all she does is review/approve stuff done by architects.
So it seems like we do have a law (at least in California) that say something like that.
Reason magazine posted an article on this:
"https://reason.com/2021/05/25/minnesota-threatens-to-fine-th..."
While I generally oppose attempts to regulate the term "engineer", I do think Reason was a little fast and loose here. It wasn't like they went in and objected to the term "sound engineer" in a recording studio or "software engineer" at google. This was a case of using a term in a situation where it could cause confusion, although even in this case, I side with the person who wants to use the term, and against the PE regulators. I do think that professional engineering associations do have the right to create a terminology. I would just be much more restrictive in scope.
I looked into regulations around Industrial Engineering, since I have an MS in this field (my undergraduate is in math). As far as I understand, licensure in Industrial Engineering is a title designation. In other words, there's no specific practice you're allowed to do as a licensed professional industrial engineer that you wouldn't be allowed to do without this license. It simply gives you the right to professionally represent yourself as a licensed PE.
I support the licensing bodies rights to restrict narrowly defined terminology that clearly references licensure, but my personal feeling is that the scope should be very limited. In other words, I believe I should be allowed to casually refer to myself as an engineer, I think it's fine to say you're a data engineer rather than a data scientist depending on what you do. I even think it's ok to refer to myself as an industrial engineer (though I wouldn't personally especially want to).
The ambiguity creeps in if I refer to myself as a "Professional Industrial Engineer". I personally wouldn't do that, it would feel a little fraudulent, but that's a feeling, not something I'd enforce through law or even social pressure. To stay on the right side of scope, I think I'd be ok with someone doing that as long as they didn't throw in "licensed".
As for "engineering" as a general term, I think it's truly absurd that PE bodies would think they have a general right to prevent others from using this descriptive term in job or work titles, it's as general as "scientist".
(wow, apparently I can't even ask...)
The complaint is that, in his advocacy, he described himself as a professional engineer, which he obviously is. The idea that one needs to stay in the good graces of the state in order to reference one's experience in their field as part of their political advocacy cannot possibly withstand genuine first amendment scrutiny, can it?
Being licensed isn't to be within the good graces of the state, it's to prove the licensee has the requite knowledge and experience to design and construct things which, when fail, people die. This is something we want in society.
First, I don't agree that licensure accomplishes this.
But second, it sounds like you agree with the plaintiff here. Nobody is asserting that he had a legal right to perform civil engineering after his license lapsed. What he's arguing is that he had a right to reference his experience in civil engineering as part of his political advocacy.
I am a Software Developer - I did not graduate from an Engineering college. I am not an Engineer. The stuff I do does not kill people when it fails.
99% of people that claim to be Engineers (at least in Software) are not.
Oh? OK technically maybe not your job specifically, but ever hear about Therac-25? MCAS on the 737-MAX?
It's all a racket. I'm an unlicensed, non-PE software engineer. Am I allowed to call myself that?
The engineering council makes it easy to get the license. Demonstrate the knowledge through a raft of exams and you will qualify. Alternatively, demonstrating 20 years of engineering experience in your field will also let you qualify.
Also, I have in fact undergone the training that an engineer in Canada would undergo. I just didn't do the tests or pay the fees, and why should I?
If you already have the education and the experience (you need both), why not complete the ethics exam and earn the license? Is it about the fees? The annual fee in California is $180.00 [1]. The annual fee in Ontario, Canada is $299.45 [2]. Does your company not pay you enough? Are you living on hardship as a software engineer to not be able to afford that?
The real question is this: Why do you feel entitled to a designation without completing the requirements for it?
[1] https://bpelsg.ca.gov/applicants/licensee_fees.shtml
[2] https://www.peo.on.ca/sites/default/files/2020-11/PEO-FeeSch...
Similarly, Doctors are still doctors even when they cross borders. They just can’t practice medicine for money without a license.
It's not.
>I'm an unlicensed, non-PE software engineer. Am I allowed to call myself that?
In many areas, yeah, you can refer to yourself as a software engineer, but the title doesn't mean anything because anyone can refer to themselves as a software engineer; there is nothing defining what that means.
This is incorrect. Check out what the PEO has to say about using "software engineer" as a title:
https://www.peo.on.ca/public-protection/complaints-and-illeg...
You can sometimes use the title without being licensed, but you have to be careful, as it can easily be considered misrepresentation.
> Where the software is used in a product that already falls within the practice of engineering (e.g. elevator controls, nuclear reactor controls, medical equipment such as gamma-ray cameras, etc.);
> Where the use of the software poses a risk to life, health, property or the public welfare; and
> Where the design or analysis requires the application of engineering principles within the program (e.g. does engineering calculations), meets a requirement of engineering practice (e.g. a fail-safe system), or requires the application of the principles of engineering in its development.
In other words, the vast majority of software engineering does not fall within the practice of professional engineering.
Which is why I qualified my statement with "many".
>You can sometimes use the title without being licensed, but you have to be careful, as it can easily be considered misrepresentation.
That is what this debate is about.