Not to me. He acted as an engineering consultant or manager in the courtroom. Managers and consultants on engineering projects rightfully require licenses, even if they do nothing but talk in meetings.
Yes, absolutely. How is that even relevant? Are you implying that it's acceptable to violate the rule of law when the government makes a mistake? Do you shoot your mailman when they mis-deliver a letter?
The reasoning is not circular, full stop. Just because the government both (1) deals in licenses and (2) can be sued in court does not make the situation logically inconsistent. You're confusing collusion/corruption for circular logic.
Right, but this is about civil engineering. I suppose that field also had tinkerers at some point, but today we expect civil engineers to have a diploma and license. Maybe software engineering will go that way too in the future, after the Internet of Unsecured Things finally implodes.
I know of a civil engineer PE who is an expert in code interpretations of the ASME (not ASCE) boilers and pressure vessels (BPVC) codes. He acts as an expert witness and also makes interpretations for clients who are unsure about the code's meaning. He makes millions because the correct design and use of such items affect lives and property at immense scales.
Safety regulations are written in blood that is too easily washed-off.
There is always a space for tinkering. I took apart clocks and small appliances when I was 5. Eventually, my dad had me rebuilding carburetors using the kits because I wasn't strong enough to rebuild alternators yet.
Last month, I made Alexa-enabled "tea candle" lanterns by gutting WiFi bedside lights and using privacy paint on said lanterns. As diffusers, I reshaped the diffusers from the original lights. Where the circuit boards appear, I painted the back walls and PCBs matte black to hide them when the lights are on. I dremeled slots in the lantern bases for USB power.
What appears to be happening is the over-regulation of title combinations to collect more money by "solving" a professionalization problem that didn't need solving.
In a lot of countries “Engineer” is a protected title. (Same in Germany where “Ingenieur” is protected). The term is usually used for mechanical engineers, and the like. Jobs you can only do with a degree, because if you fail, lives could be at stake.
We actually had a Canadian colleague request to change the job title in the employment from Software Engineer to Software Developer due to these restrictions.
That's asinine when there is no associated professional licensure requirement for cobbling together HTML for a mom&pop liquor store.
In the US, any type of (non-locomotive) engineer involved in critical engineering design, decisions, implementation, and manufacturing of large-scale or life-safety aspects can or should be a "professional engineer" (PE) so malpractice insurance (EPLI) will cover them and client/employers will hire them.
If I say I'm a witch doctor, there is no confusion that I'm not a doctor (of medicine).
My undergrad major was Computer Science & Engineering. Do I need an extra certificate to call myself "an engineer?" Nope.
Opinions and jurisdictions differ. The problem is that some jurisdiction might define “software engineering” such that an individual without a license (and not under supervision of someone with one) could get in trouble for doing software development rather than describing themselves as an engineer.
This is actually something some people want. Don’t let them achieve it.
In the US, there are a dozen or so legally-protected "engineer" title variants and professional designations like "professional engineer" (PE). My degree is accredited for the path of PE, but I would need a reason to go that route.
If it's unlisted, then it's fair to use by anyone:
Source:https://reason.com/2020/03/02/oregon-tried-to-silence-this-e...