This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.
It’s like when an intern accidentally drops the production database. It’s not the interns fault for sending the wrong command. It’s the managements fault for not restricting access in the first place.
This. This. I used to work on safety control systems for heavy industrial applications and it’s this. Once the system is running any changes at all went through a whole chain of people. When the change was being implemented I had my supervisor and their manager checking every line over my shoulder before we wrote it. Then test. Then lock it down with a digital signature.
It’s not at all like in college/university where you’re making changes to your code over and over. Well it is in simulations but that’s long before you deploy it. By the end everyone involved should be able to say exactly what every line of code is going to do. This isn’t an intern fucking up, the whole team did, and whomever the buck stops with at the top is responsible.
If you’re talking about Voyager, I’d assume so, but I don’t have any source to back that up. If you’re talking about my previous work, the test environment was exact enough… Cough not-even-close cough.
I bet you don’t simply send random commands to the probe. There are likely a dozen of people who need to approve literally every keystroke.
This. And even then there should be procedures in place to essentially make it impossible to send the wrong inputs.
It’s like when an intern accidentally drops the production database. It’s not the interns fault for sending the wrong command. It’s the managements fault for not restricting access in the first place.
This. This. I used to work on safety control systems for heavy industrial applications and it’s this. Once the system is running any changes at all went through a whole chain of people. When the change was being implemented I had my supervisor and their manager checking every line over my shoulder before we wrote it. Then test. Then lock it down with a digital signature.
It’s not at all like in college/university where you’re making changes to your code over and over. Well it is in simulations but that’s long before you deploy it. By the end everyone involved should be able to say exactly what every line of code is going to do. This isn’t an intern fucking up, the whole team did, and whomever the buck stops with at the top is responsible.
They have like a whole test environment that is an exact duplicate right?
If you’re talking about Voyager, I’d assume so, but I don’t have any source to back that up. If you’re talking about my previous work, the test environment was exact enough… Cough not-even-close cough.
“I’m gonna click approve without looking because the tons of people before / after me must have / will review it.”
… and at this moment it is no longer my problem. I have written evidence that I forwarded my command for approval.
🤦♂️