News for hackers. Stuff that matters.
Re:Rules for Developing Safety Critical Code [pdf] by HCIdivision17 on Friday January 16, 2015 @10:14AM (#8899332)
Bizarrely, I've found that most people agree this is obviously the better solution. And I have never seen it in practice (manufacturing/industry - not the shiney robotic kind, either). People often claim to want to fix the process, but it gets political fast, and because processes/systems are hard to engineer, blaming someone is just faster, easier, and cheaper.

Which is awful.

Re:Rules for Developing Safety Critical Code [pdf] by Spooky23 on Friday January 16, 2015 @11:28AM (#8899849)
The stakes are different. If pushing an error to production means that an email doesn't go out or a $500 sale goes through, you have limited motivation, as the benefit of pushing out code fast is greater than pushing it out right.

If you have a billion dollar program where a failure will kill people and create a political storm that will get your management chain fired or sidelined, you can justify spending $100M on the process (ie lots of people + less ability) to push quality.