>What is the significance of you not wanting to call it engineering?
It conflates two separate things with not a great amount of overlap. It also describes two different paths, an academic path and a tradesman path. The distinction is obviously useful in describing people/roles/activities.
You could also ask why we are conflating machinists with engineers, clearly machinists are building things, definitely more so than engineers.
> You could also ask why we are conflating machinists with engineers
You could, but it would be rather silly as machinist is clearly a subset of engineer (within what most people deem engineer to mean). It is not a conflation, it is a more precise term. Like using "surgeon" over "physician". It is not like a surgeon has anything to do with your family doctor evaluating your common cold symptoms. Those are entirely different jobs too, yet absolutely get grouped together.
The problem here, it seems, is that we've never come up with generally accepted terms to differentiate the different roles under the software engineering umbrella. I expect that is because the differentiation doesn't matter beyond trying to appeal to some pointless emotions.
> Engineering is distinguished by being an academic career.
I expect you mean that Professional Engineer (PE) is distinguished as being a member of a certain professional organization (or groups of organizations). Indeed, that is true. Has little to do with the topic at hand, though.
I'm not familiar with any differentiation by academic career, unless you are thinking of "Professor of Engineering", or something along those lines? But "professor" seems to be the operative word there.
What about the definition of engineer even suggests academics? It is, in my mind, decidedly pointed to practitioners. It literally states "design, build, or maintain". Those are decidedly not academic pursuits.
Where I live you can not call yourself an "engineer" at all without a specific university degree.
It is pointless to discuss here, if you do not see the value in distinguishing the career of learning a trade and a getting a degree, I won't convince you otherwise. Obviously the rest of the world doesn't consider a bricklayer an engineer, just because he is building something and wouldn't want to conflate the civil engineer responsible for that building with the profession of brick laying.
> Where I live you can not call yourself an "engineer" at all without a specific university degree.
Same here, but we're still going to call other people engineers because usurping a term already found in the common lexicon and trying to hold it legally hostage is the dumbest thing I've ever seen. The existence of a law does not imply sound reasoning.
> if you do not see the value in distinguishing the career of learning a trade and a getting a degree, I won't convince you otherwise.
If there was such benefit, professional engineering organizations would serve no purpose. In reality, it's the professional organization that brings benefit. After all, you can't take someone's degree away. But you can remove them from being a professional member when they don't abide by the "engineering code", which is where the actual benefit lies.
But if you want to call attention to the degree you hold for whatever arbitrary reason, why not simply say "I have a degree"? Why would "engineer" need to say the same thing? In reality nobody is going to care anyway (they might care if you are a member of a PE organization, though), but if they did for some bizarre reason, they're going to want to see proof, so your word doesn't matter anyway. There is good reason the prevailing definition of engineer does not imply anything of the sort.
It conflates two separate things with not a great amount of overlap. It also describes two different paths, an academic path and a tradesman path. The distinction is obviously useful in describing people/roles/activities.
You could also ask why we are conflating machinists with engineers, clearly machinists are building things, definitely more so than engineers.