3 ms·

There's some weird conception in the medical industry and public at large that the software has to be perfect the first time, every time. Come again? In the r

There's some weird conception in the medical industry and public at large that the software has to be perfect the first time, every time. Come again? In the real world the reliability problem has been solved. Nuclear power has been around for 60-odd years now and atomic powerplants do not regularly explode. Software on the other hand, has been around for the same time, and we expect it to be bug-afflicted. What is is that nuclear engineers have but software "engineers" are missing?

angersock 12y ago
Two centuries at least of engineering experience to build on, for a start? Nuclear plants are relatively straightforward extensions of existing civil, electrical, mechanical, and chemical engineering principles--it's all just steam engines eventually. Also, notice that there are a lot more software installations and people who work on them than nuke plants. Also also note that this supremely reliable technology you are trying to hold up is (rightly or wrongly) being demonized and phased out across the first world. The point you probably want to make is that software engineering should be a more rigorous profession. And yes, we've got a ways to go there, and yes, we're making progress. What is not reasonable is the hypocritical and self-serving risk-aversion many people have to improving processes through software.
threatofrain 12y ago
Nuclear power is, as far as I know, a consistent problem, meaning that it's not like the requirements and shape of the problem changes that much. Medical programming, on the other hand, means programming for anything medical. You cannot really pre-model the problem with a general solution, because you don't know what salient problem is going to capture social attention in the next few years. You don't know what devices are going to be created. People might have programming standards and methods for building secure systems, but I would say it's a lot easier to work around a problem that has remained mostly still. Another thing is cost-efficacy. You can always have better and more safe of anything, not just in programming. Aren't car accidents so tragic? They are also one of the prominent causes of accidental death. Well, why don't we mandate that car manufacturers must include better collision safety? We could. We could mandate until all our fears are gone. Then fewer people would have cars. Ecological and public transportation arguments aside, I don't like a world where the gateway of money requires a much higher bar to pass. Wouldn't it be unfortunate if fewer patients could access the range of medical devices which have been rigorously analyzed by a team of better-than-average engineers, and consequently the public experienced net damage?
TheCoelacanth 12y ago
We know how to create reliable software; we just don't want to pay for it. We prefer for software to be cheap than for it to be reliable, so that's what we get. In the rare cases where we do spend the extra money on quality, e.g. embedded software in vehicles, we do get reliable software.

angersock 12y ago

Two centuries at least of engineering experience to build on, for a start? Nuclear plants are relatively straightforward extensions of existing civil, electrical, mechanical, and chemical engineering principles--it's all just steam engines eventually. Also, notice that there are a lot more software installations and people who work on them than nuke plants. Also also note that this supremely reliable technology you are trying to hold up is (rightly or wrongly) being demonized and phased out across the first world. The point you probably want to make is that software engineering should be a more rigorous profession. And yes, we've got a ways to go there, and yes, we're making progress. What is not reasonable is the hypocritical and self-serving risk-aversion many people have to improving processes through software.

threatofrain 12y ago

Nuclear power is, as far as I know, a consistent problem, meaning that it's not like the requirements and shape of the problem changes that much. Medical programming, on the other hand, means programming for anything medical. You cannot really pre-model the problem with a general solution, because you don't know what salient problem is going to capture social attention in the next few years. You don't know what devices are going to be created. People might have programming standards and methods for building secure systems, but I would say it's a lot easier to work around a problem that has remained mostly still. Another thing is cost-efficacy. You can always have better and more safe of anything, not just in programming. Aren't car accidents so tragic? They are also one of the prominent causes of accidental death. Well, why don't we mandate that car manufacturers must include better collision safety? We could. We could mandate until all our fears are gone. Then fewer people would have cars. Ecological and public transportation arguments aside, I don't like a world where the gateway of money requires a much higher bar to pass. Wouldn't it be unfortunate if fewer patients could access the range of medical devices which have been rigorously analyzed by a team of better-than-average engineers, and consequently the public experienced net damage?

TheCoelacanth 12y ago

We know how to create reliable software; we just don't want to pay for it. We prefer for software to be cheap than for it to be reliable, so that's what we get. In the rare cases where we do spend the extra money on quality, e.g. embedded software in vehicles, we do get reliable software.