Authored by: Anonymous on Tuesday, April 24 2012 @ 10:40 AM EDT |
Another point is that, unlike buildings with their physical
manifestations, software never "suddenly" goes bad.
For example, a bolt holding a critical piece of a bridge in
place can "suddenly" reach its breaking point and as a
result fail, taking the bridge down. This does not mean that
the bolt was an error to begin with, only that it finally
reached a failure point.
Software doesn't work that way. If it has a bug that causes
a failure, that bug was there from day one.
On another point, having an engineering degree (a real one,
lol), and having written software for medical devices and
process control, it is ALWAYS in the back of my mind that if
I write my software poorly, failures may lead to deaths.
Unfortunately, for a lot of software developers (I refuse to
call them or myself a software engineer), they seldom think
of external consequences of poor coding.[ Reply to This | Parent | # ]
|
|
|
|