Re: [SystemSafety] OpenSSL Bug

From: Les Chambers < >
Date: Sat, 19 Apr 2014 08:12:50 +1000

Yes, Everyone Has Their Own Truth - changing someone else's is extremely difficult.
I have put a small piece on the process of influence here: ... The thoughts of Aristotle et al
I am extremely proud of the illustration. The Seņorita was captured, with available light, after midnight in Girona from a range of 50 m with a long lens.

-----Original Message-----
From: systemsafety-bounces_at_xxxxxx [mailto:systemsafety-bounces_at_xxxxxx Chris Hills
Sent: Thursday, April 17, 2014 4:38 PM
To: systemsafety_at_xxxxxx Subject: Re: [SystemSafety] OpenSSL Bug

I agree with Todd the biggest problem is the attitudes of the people. We have seen this with the development of Agile and people actually wanting to use it for critical systems.

At one time we had Analysts and programmers. Now the Analysts seem to have gone and SW developers seem to thing SW is all about writing code. Whereas on a SW project it should be 86% requirements and design and 15% coding and unit test.

Until there is a sea change in the way the majority of software is developed no change in processes will work.

BTW the process is fixed.... the V model works well but most don't have the discipline to work to it. BTW I talk to a LOT of developers from a LOT of companies. I visit them all the time and see the same things repeated time after time.

To be fair it is not all the programmers. Often middle and senior management are looking for cheap, short cuts and "efficiencies". Then the problem is the Programmers don't seem to be able to explain their own profession to others to show why money needs to be spent or what appears to be expensive time consuming steps are worth doing in the long run. Then again for the average British accountant "long term" is 3-6 months :-( .


-----Original Message-----
From: On Behalf Of Todd Carpenter

If we fix the person, then wouldn't part of the problem stop reproducing itself? :)

On 4/16/2014 5:32 PM, Steve Tockey wrote:
> Instead of blaming the person, how about we blame the process? And
> then take active steps to fix the process?

The System Safety Mailing List

The System Safety Mailing List
systemsafety_at_xxxxxx Received on Sat Apr 19 2014 - 00:13:12 CEST

This archive was generated by hypermail 2.3.0 : Tue Jun 04 2019 - 21:17:06 CEST