<story><title>Erlang programmer’s view on Curiosity Rover software</title><url>http://jlouisramblings.blogspot.com/2012/08/getting-25-megalines-of-code-to-behave.html</url></story><parent_chain></parent_chain><comment><author>pron</author><text>I absolutely love Erlang and think that, along with Clojure, it provides a complete ideology for developing modern software.&lt;p&gt;But the article implies (and more than once) that the rover&apos;s architecture borrows from Erlang, while the opposite is true. Erlang adopted common best practices from fault-tolerant, mission-critical software, and packaged them in a language and runtime that make deviating from those principles difficult.&lt;p&gt;The rover&apos;s software shows Erlang&apos;s roots, not its legacy.</text></comment>
<story><title>Erlang programmer’s view on Curiosity Rover software</title><url>http://jlouisramblings.blogspot.com/2012/08/getting-25-megalines-of-code-to-behave.html</url></story><parent_chain></parent_chain><comment><author>Tloewald</author><text>Back in the 90s there was a software engineering fad (unfair term but it was faddish at the time) called the process maturity index, and JPL was one of two software development sites that qualified for the highest rank (5) which involves continuous improvement, measuring everything, and going from rigorous spec to code via mathematical proof.&lt;p&gt;This process (which Ed Jourdan neatly eviscerated when applied to business software) produces software that is as reliable as the specification and underlying hardware.</text></comment>