'Paranoid Programming Practices'
I don't know what JPL and NASA (perhaps others) call their software coding style, but there have been many examples of their paranoid approach, where the programmers don't even trust themselves, saving missions. The usual 'Safe Mode' is just the tip of the iceberg; there seems to be many layers of paranoia built into their typical code, based on what I've read about their occasional mission emergencies (and how the software often helps in surprising ways). The same approach extends into the hardware architecture and design of course, but that's not as impressive as the software coders own rigorous hubris-elimination practices (opposite of *a* stereotype).
Somebody ought to formalize this process in a text book, 'Paranoid Programming Practices'.
Biting the hand that feeds IT
