The Software Behind the Mars Phoenix Lander
chromatic writes "Imagine managing a million lines of code to send over seven hundred pounds of equipment millions of miles through space to land safely on Mars and perform dozens of experiments. You have C, 128 MB of RAM, and very few opportunities to retry if you get it wrong. O'Reilly News interviewed Peter Gluck, project software engineer for NASA's Mars Phoenix Lander, about the process of writing software and managing these constraints — and why you're unlikely to see the source code to the project any time soon."
/ You seem to be trying to make a joke \
| would you like me to: |
| o Help me come up with new jokes |
| o Help me bash Bill Gates |
| o Help me spell Microdollarsignoft |
| o No thanks, let me keep making |
| a redundant ass of myself |
\ P.S.: **** open sores /
\
\
\ ____
\ / __ \
\ O| |O|
|| | |
|| | |
|| |
|___/
--
cpu0: Microsoft Clippium ("GenuineClippy" ChromedMetal-Class). Paperbinding, lockpicking, fish-hook-hack support.
template greedily stolen from this guy: http://slashdot.org/~ClippySay
if they wrote it in perl, it would only be 1 line.
The Kruger Dunning explains most post on
#include void main() { printf("Hello Mars\n"); }