When Programming for NASA, Contingencies Pile Up
Jun 03, 2008, 18:45 (0 Talkback[s])
(Other stories by Mark Hall)
[ Thanks to StonyandCher for this link.
"Suppose you were developing software that would run about 50 to
60 operational tasks simultaneously, including the management of
multiple mechanical and digital devices. That'd be reasonably
complex. Now consider that any time a task stumbled, the software
would have to correct itself. That would mean thinking ahead for
every possible contingency that could affect all running tasks and
designing in self-healing capabilities. That's much more
"And by the way, your application will be running on Mars, so
on-site service is going to be a bit of a problem..."