 |
Date Posted:
Tuesday October 02, 2001 01:53:44 PM
|
|
I'm a little late and somewhat "green" for this discussion of licenses but I thought I might add an idea along. My presentation is quite simplified but only for purposes of getting the idea across.
Software, as opposed to medicine, hairdressing, plumbing, etc. is by nature a "Swiss Army knife". It is used in a wide spectrum of situations that can be radically different. While it can be used to control pressure valves in phosphate plants, it can also be used to run online role-playing games.
These two situations raise different concerns at a public level. If the software used in the pressure valves were to fail to meet its intended objectives correctly, this might generate a truly dangerous situation with lives at risk. If an RPG (role-playing game) site were to go down, the repercussion would probably be limited to a bunch of angry customers and its consequences.
I would support software engineering certification for those engineers and their firms whose work is going to be applied in situations where there are potential risks and/or dangers to human populations and/or critical infrastructures (including things such as financial services) as long as it doesn't impede the free and unencumbered development of non-critical applications by non-certified engineers. What is and isn't considered critical is sure to be argued about but perhaps this is a way out of the certificate/non-certificate dichotomy.
|