|
|
|
|
|
|
by stale2002
3002 days ago
|
|
|
That is a small subset of software. The vast majority of software written today has precisely 0 ability to kill anyone. Even IF you are working at a company doing one of those things, only a subset of engineers that are working there are going to working on the "core" part of the software. Those companies have lots of web developers making code that isn't dangerous as well. To put it another way, reading and writing can kill as well. If the person writing the airplane manual screws up, it could kill someone. But does that mean we need a bar exam of writing English? |
|
|
There's lots of ways software can cost corporations money if it fails to operate. The recent failures at Delta, Southwest, United, all come to mind. The IT industry has a myriad of certifications to, say, prevent some tech-idiot from touching the routing table on the routers.
The ISO has standards for software engineering (similar to ISO9001 for hardware) but so far the market does not feel that standard provides a competitive advantage. If I could guarantee my processes gave you 99.9999% uptime with our software, would you prefer that or another company that can iterate faster?