Re:Rules for Developing Safety Critical Code [pdf]
by thearn4 on Friday January 16, 2015 @08:16AM
(#8898625)
As a software person at NASA, one caveat to note is that this is in part due to the intricacies of the federal civil servant system. Frankly, it is very hard to punish or fire government employees or some prime contractors, so most often (even in non-software contexts) accountability is applied to a process rather than to an individual because it's a path of less resistance for management. Even when an individual approach would be more appropriate.
[ Parent
| on HN ]
Re:Rules for Developing Safety Critical Code [pdf]
by Spooky23 on Friday January 16, 2015 @11:23AM
(#8899819)
The other nuance here is focusing on process gives you a place to put less capable people that you're stuck with. You can create tightly defined QA tasks that are easily verified, give people a checklist, and keep them away from places where they can break things.