A Look into NASA’s Coding Philosophy
Here&#x27;s a paper[1] for a space conference in Montreal written a few years ago on DO-178 standards and applying the FAA&#x27;s certification process to space systems development (DO-178 sets the bar for &quot;testing the shit&quot; out of software, I&#x27;ve seen projects held up for years because it&#x27;s like approaching a limit f(n) -&gt; L (where f(n) is the software development cycle and L is getting a non-bought DER to sign off on it) proving your system to its requirements).<p>[1] <a href="http:&#x2F;&#x2F;articles.adsabs.harvard.edu&#x2F;cgi-bin&#x2F;nph-iarticle_query?2013ESASP.715E..63D&amp;amp;data_type=PDF_HIGH&amp;amp;whole_paper=YES&amp;amp;type=PRINTER&amp;amp;filetype=.pdf" rel="nofollow">http:&#x2F;&#x2F;articles.adsabs.harvard.edu&#x2F;cgi-bin&#x2F;nph-iarticle_quer...</a>