/Jason Kottke

How NASA Writes Space-Proof Code tl;dr: The rules focus on testability, readability, and predictability: (1) Avoid complex flow constructs, such as goto and recursion. (2) All loops must have fixed bounds. This prevents runaway code. (3) Avoid heap memory allocation. (4) Restrict functions to a single printed page. (5) Use a minimum of two runtime assertions per function.

featured in #428