Re:A short fable of software engineering vs. regular enginee...
by catnaroek on Sunday January 10, 2016 @08:27PM
(#10878228)
> We know how to build reliable (nearly) bug-free software.
Do we? Let's say, starting tomorrow, you have to write rocket-guiding software. If your program has bugs, you will be summarily executed. What are the odds that you will survive the process? I wouldn't estimate mine at anything significantly above zero.
Re:A short fable of software engineering vs. regular enginee...
by dllthomas on Monday January 11, 2016 @03:44AM
(#10879622)
How long can I take?
Re:A short fable of software engineering vs. regular enginee...
by catnaroek on Monday January 11, 2016 @07:56AM
(#10880500)
I have no idea how much time this would take in the real world. Pulling a number totally out of my ass, let's say five years. You may not use subcontractors to develop the software.
Re:A short fable of software engineering vs. regular enginee...
by dllthomas on Monday January 11, 2016 @11:43AM
(#10881479)
Well, then I'm pretty confident I could survive at least five years... :P
Re:A short fable of software engineering vs. regular enginee...
by catnaroek on Monday January 11, 2016 @01:24PM
(#10882102)
Which I guess is enough time to buy life insurance. At least your family won't have money problems. :-)
Re:A short fable of software engineering vs. regular enginee...
by dllthomas on Monday January 11, 2016 @08:08PM
(#10884874)
To be honest, for commensurate reward, I'd probably be sufficiently confident that I could get something done bug-free in 5 years if it was something that I felt could hack out bug-full in a week. Much of that time would go toward task-specific verification-related tooling...
The problem is, for most things, it's too expensive. What we have is good enough.