Everyone who writes safety critical software should read this
Brad Roberts
braddr at puremagic.com
Tue Oct 29 17:28:16 PDT 2013
On 10/29/13 5:15 PM, Joseph Rushton Wakeling wrote:
> On 29/10/13 23:20, Chris wrote:
>> Good man yourself! I still can't get my head around the fact that companies fail
>> to provide safety switches that either hand over the control (to humans) or at
>> least disable the software based components completely by switching the machine
>> off.
>
> All too often, the reason why management decides to use software to perform tasks is because they
> don't trust their employees to do anything.
>
> It's a mystery to me why they don't start by finding employees they _do_ trust ... :-)
As long as you're relying on trust, you're in trouble. Trust and verify. Of course, you have to
trust the verification, but that trust can in turn be validated (harder to falsify stress to failure
results than "yeah, it'll work" assertsions). It's part of why testing exists.
More information about the Digitalmars-d
mailing list