> 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.

[1] https://en.wikipedia.org/wiki/2015_Office_of_Personnel_Manag...

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-...

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.