In fact, in some Canadian provinces, titles in computing such as “software engineer,” “computer engineer,” and others containing “engineer” are (in principle) reserved for people licensed as engineers by the provincial engineering regulator.
A most rational stance. One we should enforce here in the US.
--
If I were an engineer, there's no way I would trust any interface to a control system for a water purification plant that connected to the internet and allowed for ingress of control. Just as an example.
The OPM hack of 2015[1] is the worst case, in terms of national security, that clearly proves no Engineers were involved in the design of their computer system. Ingress of control should be absolutely prohibited, and it wasn't. I don't know why that database was ever put into a computer, instead of filing cabinets in a vault, nor why it was ever connected to any other system, and not completely air-gapped in said vault, with manual controlled exfiltration of data upon request.
The difference is for others than "engineers" (software developers), where there is an expectation of certain quality when they hear someone call themselves "engineer". Just like the title "doctor" carries a certain expectation.
"Doctor" is a funny one because physicians originally latched onto the term to try and give themselves the credibility where they previously had none. Its use in medicine is in a lot of ways similar to the software situation.
So what about like "mechanical engineers" or "process engineers" or "hardware engineer" or "biomedical engineers" etc?
I don't know why that database was ever put into a computer, instead of filing cabinets in a vault, nor why it was ever connected to any other system, and not completely air-gapped in said vault, with manual controlled exfiltration of data upon request.
I suspect this is not because of the fake engineers but rather because other forces, e.g. management wanted more efficiency and security was the last item on the list. I don't see how changing job titles would change anything here
There's internet-connected industrial control panels online where you can just connect to them on your browser or some tool and start clicking buttons.
it's probably just convenient because there's no auth or VPNs required. yippee!
SCADA (Supervisory control and data acquisition) goes back to the 50s with, yes, remote access. Security has never been a design factor (after all, how many people had mainframes in the 50s?).
I notice that software-related professions tend be named after traditionally male-dominated fields, such as "software engineer" or "software architect" or even the "rock star programmer".
Which is strange since the original "computers" were predominately women[0] and I find writing software has much in common with activities that were historically at least coed, such as creating recipes or sewing patterns.
Yet we never hear of "software chefs" or "software tailors". Given how little many titular heads of software companies understand their product, "software nanny" would also be applicable.
Maybe it's cultural or geographic, but both "chefs" and "tailors" is similarly male dominated here (Serbia in Europe). Out of all the professions you bring up, architects are actually pretty evenly split here.
Obviously, what matters is where the term was coined, but I'd certainly suspect it has nothing to do with any gender bias and is instead about parallels to civil construction: architects design, engineers make it work and possible for builders to build. If anything, with LLMs, software engineers more closely match up to construction (as engineers rarely lay a single brick).
I think only some software work is engineering and if I call myself a software engineer (in regard to my employment), it’s because it’s actually “a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”. And not just paying lip service. Otherwise, I’m something else with or even without the word software in the title (even if I work with software). Outside of work, I inherently consider myself a software engine but if work requires it, I have no problems treating it as less.
A most rational stance. One we should enforce here in the US.
--
If I were an engineer, there's no way I would trust any interface to a control system for a water purification plant that connected to the internet and allowed for ingress of control. Just as an example.
The OPM hack of 2015[1] is the worst case, in terms of national security, that clearly proves no Engineers were involved in the design of their computer system. Ingress of control should be absolutely prohibited, and it wasn't. I don't know why that database was ever put into a computer, instead of filing cabinets in a vault, nor why it was ever connected to any other system, and not completely air-gapped in said vault, with manual controlled exfiltration of data upon request.
[1] https://en.wikipedia.org/wiki/2015_Office_of_Personnel_Manag...
So instance of SWE1 we become SWD1. I don't see the difference.
The difference is for others than "engineers" (software developers), where there is an expectation of certain quality when they hear someone call themselves "engineer". Just like the title "doctor" carries a certain expectation.
"Doctor" is a funny one because physicians originally latched onto the term to try and give themselves the credibility where they previously had none. Its use in medicine is in a lot of ways similar to the software situation.
Barber-surgeon doesn't have the same vibe, I suppose.
So what about like "mechanical engineers" or "process engineers" or "hardware engineer" or "biomedical engineers" etc?
I suspect this is not because of the fake engineers but rather because other forces, e.g. management wanted more efficiency and security was the last item on the list. I don't see how changing job titles would change anything here
The infrastructure-getting-hacked thing is wild to me! Something went very wrong early in the design process!
There's internet-connected industrial control panels online where you can just connect to them on your browser or some tool and start clicking buttons.
it's probably just convenient because there's no auth or VPNs required. yippee!
SCADA (Supervisory control and data acquisition) goes back to the 50s with, yes, remote access. Security has never been a design factor (after all, how many people had mainframes in the 50s?).
So yes, from very early in the design process.
Hillel Wayne did a series of interviews with people who are considered "proper" engineers, which you can read here:
https://www.hillelwayne.com/tags/crossover-project/
the tl;dr is that for the most part, modern software development is very similar to engineering
I notice that software-related professions tend be named after traditionally male-dominated fields, such as "software engineer" or "software architect" or even the "rock star programmer".
Which is strange since the original "computers" were predominately women[0] and I find writing software has much in common with activities that were historically at least coed, such as creating recipes or sewing patterns.
Yet we never hear of "software chefs" or "software tailors". Given how little many titular heads of software companies understand their product, "software nanny" would also be applicable.
[0] https://www.smithsonianmag.com/science-nature/history-human-...
Maybe it's cultural or geographic, but both "chefs" and "tailors" is similarly male dominated here (Serbia in Europe). Out of all the professions you bring up, architects are actually pretty evenly split here.
Obviously, what matters is where the term was coined, but I'd certainly suspect it has nothing to do with any gender bias and is instead about parallels to civil construction: architects design, engineers make it work and possible for builders to build. If anything, with LLMs, software engineers more closely match up to construction (as engineers rarely lay a single brick).
I think only some software work is engineering and if I call myself a software engineer (in regard to my employment), it’s because it’s actually “a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”. And not just paying lip service. Otherwise, I’m something else with or even without the word software in the title (even if I work with software). Outside of work, I inherently consider myself a software engine but if work requires it, I have no problems treating it as less.