4 ms·
> Held to the same standard as civil engineers Impractical comparison. Software engineers rarely create works where loss of life, or even physical harm, is a s
by dgzl 8y ago
> Held to the same standard as civil engineers
Impractical comparison. Software engineers rarely create works where loss of life, or even physical harm, is a side effect of poor workmanship.
- rectang 8y agoIs losing your home insignificant? I would be shocked if out of hundreds of foreclosures, there were no suicides.
- dgzl 8y agoIn this case, you could loosely say that foreclosure was a direct result of the software bug. Suicide would be an indirect result. Where if a bridge were to collapse, then death would be a direct result.
- geggam 8y agoReally ? Everything I use today seems to have some micro processor thing in it. Cars can run into things and typically this causes damage and can cause loss of life, as an example where bugs can kill folks.
- dgzl 8y agoYour example with cars would only make sense if a software bug put a driver in direct danger without giving them time to be responsible and mitigate the danger. In almost all situations, even with modern technology in cars, it's the driver's responsibility to drive/steer/brake to mitigate the danger. How many pieces of software exist in this world where there is zero chance of even a catastrophic bug causing harm to humans? I would bet most of the existing pieces fit this description. Now apply that question to works of civil engineering, and you have a different picture.