Seriously, this whole "my culture says you need this certification X to be an engineer so you can't be one if you don't have it" is just a stupid definitional debate. It doesn't even matter if you win... nothing changes! Not a single person will lose their job Monday or even so much as change their title even if you somehow "win". So who really cares?
They seem to forget that military engineers are "engineers", and they've apparently been around since the early 1600s [1]. And locomotive engineers are "engineers", and it looks like they don't even need post-secondary schooling [2].
And the rules around the P.Eng. titles are provincially regulated as opposed to federally, meaning the rules in Ontario (where apparently the term "Engineer" is protected) is different than in Alberta (where the protected term is "Professional Engineer").
That's why in Alberta, Raymond Merhej was sued for using the title "systems engineer" (as an Apple Canada-certified systems engineer) but the suit was dismissed in late 2003. In response, the Association of Professional Engineers, Geologists and Geophysicists of Alberta (APEGGA) said basically they'll lobby the government to amend the laws to prevent that in the future. [3] I don't know if such an amendment was ever completed though.
I wonder if engineers in traditional fields are protective of their title because they work with a lot of engineering technicians, so they feel they need to differentiate and protect their work?
[1] http://cmea-agmc.ca/our-heritage-and-our-stories
[2] http://www5.hrsdc.gc.ca/noc/english/noc/2011/Profile.aspx?va...
[3] http://www.itbusiness.ca/news/it-industry-wins-round-in-engi...
Seriously, what was the point of your posting that YET AGAIN? Could you not infer that I already knew that from the contents of my post? You're moving beyond tedious into making me wonder if there isn't actually something a bit wrong with you people who can't stop talking about this when it's not even on topic.
For instance, I wouldn't be allowed to call myself a Structural Engineer or practice as a Structural Engineer without the proper licensing. Industrial Engineering, on the other hand, is just a title restriction - you need to pass the Industrial Engineering PE to call yourself one, but there's no restriction on practice associated with it [1]
But yeah, generally speaking, sticking the word "engineer" after something is allowed here. You can be a "special effects engineer" or a "sanitation engineer" or whatever. "Software Engineer" is actually controlled in a few states, though.
One other thing to keep in mind is that in the US, elite universities like MIT, Stanford, Berkeley, and so forth typically offer a CS degree, but not a software engineering degree - though top CS programs are often ABET accredited.
For one thing, engineer is not a protected term in the US. It's not at all like the fraud which would be committed by a nurse calling himself a surgeon.
More importantly, the majority of excellent US universities don't even have a "software engineering" degree. Almost universally, the good developers I see coming out of top universities majored in "computer science."
Anecdotally, most people with "software engineering" degrees come from shitty vocational programs.
We'd all be better off if we stopped fussing over titles and realized that the only reasonable way to evaluate someone is to look at their actual experience/education.
What you say may be true in Canada, but I'm pretty sure at best the opposite is true in the US (in terms of direction of attrition). But it's probably better to just admit that different fields are different, and rank-ordering is nothing more or less than a way to start flame wars and make people feel inferior for not being like you.
edit: also, your analogy is completely absurd. Even in Canada, the schooling/accreditation disparity between RNs and doctors is completely incomparable to the schooling disparity introduced by choice of undergraduate major...
So the amount of stuff you study is about is more broad because you are studying other somewhat unrelated topics.
It's more like working 60hrs/wk vs 40hrs/wk as a nurse. Your still just being a nurse.
First year engineering courses in Canada, at least at the universities I know of, are pretty similar across all of its sub-disciplines. At UBC, first year courses include 4 physics courses (1 of which is a lab course) and 1 chem course [1]. At U of Alberta, first year courses include 1 physics course, 2 mechanics courses, and 2 chem courses [2].
At both UBC and U of A, first year engineering students get to take just one course on computing science/programming. So if you love to code and go into engineering to become a software engineer in Canada, you better also at least tolerate taking a bunch of chemistry and physics/mechanics courses...
[1] http://students.engineering.ubc.ca/registering-courses
[2] http://www.engineering.ualberta.ca/ProspectiveStudents/First...
[1] Well, not me personally, I do hold an electronics engineering degree.