Agile programming (was Re: [P|C] Banksel)
Jake Anderson email (remove spam text)
Alan B. Pearce wrote:
I have been trying to work out why it is we can't make reliable
software, but we can (generally) build a bridge that is going to last
It comes down to margins. When you are building something you say, well
this beam has a load of X so I'll put a beam in that will take 2X as a
load without breaking. Then down the track when it turns out the builder
is using particularly heavy bricks that beam sees 1.3X the load it was
meant to see everything is still handled.
What I am yet to see is how you can apply "margin" to software design,
its too "perfect" a system in many respects, If you miss one check to
see if a number is zero before doing a divide your hosed. Sure you can
try and "handle" those kinds of errors, but that seems more like
propping up the building after the balcony has fallen off.
You can apply margin to things like speed and the like but the only
program/system I'm aware of that feels like it has that "2x" safety
factor was the lunar module guidance computer.
Anybody have any thoughts on "margin" as it applies to software?
In reply to: <FCB48E2BA4A44D9FA56F161C9E9FEA45@space.rl.ac.uk>
See also: www.piclist.com/techref/microchip/devprogs.htm?key=programming
You must be a member of the
piclist mailing list
(not only a www.piclist.com member) to post to the