At a guess, an increased probability of causing a criticality accident as a result of getting a program slightly wrong.

I'm assuming the "reading assembly" part is verifying compiler output matches what the programmer thinks and signing it off as a "blessed binary".

Some safety critical areas of software are done this way, in aerospace for example. But run-of-the-mill automation jobs aren't.

bit flips from surplus neutrons? TMR? Batshit crazy lack of process checks on 'what does this button do'

war stories.

actually, I encourage anyone in coding to share run-of-the-mill maintenance of outdated industrial automation, as a gig. I'd read that blog.