the best way to avoid being that guy is to make sure your software safety auditing is better than everyone else's.
I suspect that a more popular answer is "make sure your software is used in an environment where the worst-case failure mode isn't that bad."
Which sorta loops back to the licencing issue again - I'm pretty sure that a lot of software has licence clauses like "don't use this software for any medical purpose" too...
Edited to Add: I mean "more popular" in the sense that "more people do this". Which is bleedin' obvious, now that I think about it, because most software probably exists in a reasonably "safe" environment.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
branchandroot
no subject
Date: 2012-04-15 15:34 (UTC)I suspect that a more popular answer is "make sure your software is used in an environment where the worst-case failure mode isn't that bad."
Which sorta loops back to the licencing issue again - I'm pretty sure that a lot of software has licence clauses like "don't use this software for any medical purpose" too...
Edited to Add: I mean "more popular" in the sense that "more people do this". Which is bleedin' obvious, now that I think about it, because most software probably exists in a reasonably "safe" environment.