[SystemSafety] Another unbelievable failure (file system overflow)

[Robert Schaefer at 300]

I would claim that this not always prospect theory sometimes dysfunction due to greed.


By deliberately not testing you can get the customer to:

 1. become your beta tester, i.e. work for you for free

 2. directly or indirectly get the customer pay you again for you fixing your own mistakes

 3. You leave no evidence of criminal negligence (when you are indeed criminally negligent ->

      if you did detect safety issues during testing, those issues would be recorded in the testing documentation).


I would like to see, someday, a serious socio-economic study of the insights of the Dilbert comic (dilbert.com).

I have read in interviews with the cartoonist (Scott Adams) that  people email him what they've experienced,

and he just draws it up. One might claim that what he does is all made up, but I have my doubts given what

I've experienced as a programmer in several large corporations over the past decades.


________________________________
From: systemsafety-bounces at lists.techfak.uni-bielefeld.de <systemsafety-bounces at lists.techfak.uni-bielefeld.de> on behalf of Matthew Squair <mattsquair at gmail.com>
Sent: Friday, May 29, 2015 2:13 AM
To: Heath Raftery
Cc: systemsafety at lists.techfak.uni-bielefeld.de
Subject: Re: [SystemSafety] Another unbelievable failure (file system overflow)

An example of prospect theory?

Matthew Squair

MIEAust, CPEng
Mob: +61 488770655
Email; Mattsquair at gmail.com<mailto:Mattsquair at gmail.com>
Web: http://criticaluncertainties.com

On 29 May 2015, at 7:43 am, Heath Raftery <heath.raftery at restech.net.au<mailto:heath.raftery at restech.net.au>> wrote:

On 28/05/2015 11:50 PM, Chris Hills wrote:
Static analysis isn't free. Testing isn't free.
Who determines the need for  or business case for static analysis and test?
[CAH] normally (every report I have seen) static analysis saves a lot of
time and money.
The same is true of structured testing.

Funnily enough, the only experience I've had recommending static analysis is as the programmer to the manager. This is indeed the argument I use. A strange thing happens in business though (and perhaps my lack of comprehension explains why I'm the programmer and not the manager ;-) ) - capital costs and investment are worse than running costs. Buying and applying static analysis, even if it is cheaper in the long run, is always seen as less attractive than paying labour to deal with the consequences later.

Heath
_______________________________________________
The System Safety Mailing List
systemsafety at TechFak.Uni-Bielefeld.DE<mailto:systemsafety at TechFak.Uni-Bielefeld.DE>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20150529/79532040/attachment.html>