3 ms·
I also heartily agree with him that software's general laxity with regards to reliability is contagious. I've come think that calling it all "software" is dange
by wpietri 8y ago
I also heartily agree with him that software's general laxity with regards to reliability is contagious. I've come think that calling it all "software" is dangerous, like thinking of all things made with atoms as the same.
I think we as an industry should get together, divide the work into various domains, and establish professional and ethical standards for the domains that matter. Standards with teeth, such that developers who want to do the right thing in the face of bosses insisting otherwise have the backing of their peers. And also such that developers who don't care about the right thing fear the professional consequences.
I honestly think this is something we should do regardless. But as a practical matter, if we don't governments will do it for us soon enough. Software keeps getting more important, as do its failures.
- ubertakter 8y agoSomething like (or exactly) software systems safety methods should be applied to critical systems (such as aircraft systems). DoD does this for all of their critical software. And I say "something like" only to indicate there may be something particular about software in aircraft. I doubt it though. And as the article indirectly points out, analysis was severely lacking. DoD Software System Safety handbook https://www.acq.osd.mil/se/docs/Joint-SW-Systems-Safety-Engineering-Handbook.pdf https://www.acq.osd.mil/se/docs/Joint-SW-Systems-Safety-Engi... Full disclosure: The company I work at does this type of work. I don't work in that group.
- xiphias2 8y agoWe already have standards, one of which is clear technical documentation of the system, which the users were not getting. Also we have standards for writing fault tolerant systems (I would say even 2 measure devices are not enough, you need at least 3 to be able to decide). In Boeing it's clear that software best practices and standards were not followed at all. As an example here's the description of the Google Test Certificstion process: https://mike-bland.com/2011/10/18/test-certified.html https://mike-bland.com/2011/10/18/test-certified.html
- uxp100 8y agoI don't know that this hasn't been done already. If you're working on automotive software, for example, you will comply with ISO 26262. Is this the type of professional standards you are referring to?