[rubyist5eva]

Canadian developer here. I always correct people when they call a developer a software engineer for specifically this reason. I've met exactly one person in my entire career that was actually a licensed engineer working in software. I always get the glazed over eyes look when I tell people that it is actually illegal to claim you are an engineer when you aren't because it's a regulated professional term, but I do it anyway because I think it's important. My father is a licensed mechanical engineer and he's allowed me to be on the periphery of his work, so I have second hand knowledge of how "loaded" the title is and why it is regulated to this degree.

[_tom_]

The distinction is a good one, but the word "engineer" has a long history and varied uses. The guy who runs a train is an "engineer", is he licensed? (maybe he is).

It would be better to create a specific term, like "registered professional engineer (RPE)" that is unique, rather than trying to limit the usage of a common word. This is what I think most places do.

[rubyist5eva]

There is a term, it's "Professional Engineer" or P. Eng. Someone who is a "locomotive engineer" must also be licensed but I think the exception in terms of vocabulary is historical rather than practical.

The word may be "common" but it is also regulated and defined in law.

[Myrmornis]

I think that the term software engineering is helpful in distinguish between building complex systems composed of many software entities versus writing code for a single application. I totally acknowledge that within-application structure can be both complex and sophisticated: I suggest that people writing such applications call themselves software engineers and not "developers" or "programmers".

[rubyist5eva]

It's not about complexity, sophistication or quality - it's about liability when shit hits the fan and your bugs kill someone.