<story><title>Making robust software: the “Mars Code” talk (2012)</title><url>http://www.verticalsysadmin.com/making_robust_software/</url></story><parent_chain></parent_chain><comment><author>atsaloli</author><text>Dr Holzmann&amp;#x27;s &amp;quot;The Power of 10: Rules for Developing Safety-Critical Code&amp;quot; was published in June 2006 issue of IEEE Computer Society &amp;quot;Computer&amp;quot; magazine. It is a small standard, easy to understand and remember; mechanically verifiable; and measurably effective. &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;spinroot.com&amp;#x2F;gerard&amp;#x2F;pdf&amp;#x2F;P10.pdf&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;spinroot.com&amp;#x2F;gerard&amp;#x2F;pdf&amp;#x2F;P10.pdf&lt;/a&gt;</text></comment>
<story><title>Making robust software: the “Mars Code” talk (2012)</title><url>http://www.verticalsysadmin.com/making_robust_software/</url></story><parent_chain></parent_chain><comment><author>SeanDav</author><text>&amp;gt; &lt;i&gt;&amp;quot;The color coding green&amp;#x2F;yellow&amp;#x2F;red had a psychological effect. The software developers worked really hard to make all the buttons go green.&amp;quot;&lt;/i&gt;&lt;p&gt;There is a possible risk element of Cargo Cult&amp;#x27;ing here. I would hope that all programmers understood &lt;i&gt;why&lt;/i&gt; the buttons weren&amp;#x27;t green. It sounds like they would have, having been certified, and in an environment that lives and breathes code safety, but it is always worth being aware that metrics like that can have hidden consequences.</text></comment>