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...
> 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
Calling yourself a „dipl. Ing. <X>“ would be a crime if you don’t possess the appropriate degree.
American employment licencing needs urgent review, and fewer licenced professions, not more.
So yes, from very early in the design process.
it's probably just convenient because there's no auth or VPNs required. yippee!
It seems reasonable to want licensure on the belief that it raises quality.
It seems unreasonable to expect people to conform to your language preferences.
Thankfully I didn't get that job and my life trajectory continued upward. Unfortunately for that team they needed exactly what their manager was critical of - some semblance of rigor around the software they built. Of course I would indeed prefer that people who build airplanes and bridges are held to a high standard for doing their job but a person building what is essentially a glorified spreadsheet in app form might not consistently need the same.
https://www.hillelwayne.com/tags/crossover-project/
the tl;dr is that for the most part, modern software development is very similar to engineering
It was two years longer than computer science, and all of those extra courses were with the “mainstream” Engineers.
Wishful thinking and brand inflation. Same thing that makes machine learning artificial intelligence.
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-...
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).