Plenty in an absolute sense, sure. I don't appreciate the implication I was being dishonest, but let's really be honest.

If you pick a random software developer in 2018, they're writing forms over data web apps for a line of business application. It's a fluffy job with no real physical danger. That was my point.

And the same applies to "shop" workers, which can mean anything from retail to machine shops. You seem to have employed a rather narrow interpretation of that term, an interpretation which perhaps is culture-specific, but whose context is not specified in the posts that started this thread.

You know I specifically said "machine shop" in my original comment so I'm not sure why you're talking about retail.

Because no one before you said "machine shop", you're the one who interpreted "shop" in an overly narrow sense and then ranted about it as if that's what everyone was talking about.

100% of those software engineers have a plethora of safety checks that are applied continuously and repeatedly before their work is ever used in an environment where any harm might actually be done to anyone.

Someone operating a backhoe for example might dig into a gas main, swing their boom around and crush or decapitate someone, swing it across power lines and electrocute themselves, etc.

Yes, mission critical software can kill people if it's not done right. That never happens because the developer was tired of a morning.

So, back at ya with that honesty bit.

> 100% of those software engineers have a plethora of safety checks

Well, this is simply not true. I suspect you conjured that figure out of thin air. Case in point, the famous Therac-25 accidents caused by a software bug causing large over-irradiations of cancer patients : https://en.wikipedia.org/wiki/Therac-25

Yes, software from 40 years ago is absolutely relevant to this discussion. You think there are a lot of developers using those same practices today?

Bugs happen, but with software you have several layers of safety checks to prevent them from becoming dangerous or fatal. A common one is having the code reviewed by one or more other developers. The odds of all those developers being unable to detect bugs at 9 AM are kind of long, wouldn't you say?

Not really, sad to say. I had a PR approved during the day yesterday by one of the smartest guys I've ever worked with and that passed all tests yet, due to a subtle issue, caused a problem in production this morning. It wasn't the end of any worlds, but this kind of thing happens all the time with complex systems.

I guess as long as those catch 100% of the issues. Even still you're solving the problem on the backend instead of the source.