3 ms·
So, I'm building a radiation therapy machine, and I want to make sure the software controlling it dispenses the right amount of radiation, not 100 times the rig
by philwelch 14y ago
So, I'm building a radiation therapy machine, and I want to make sure the software controlling it dispenses the right amount of radiation, not 100 times the right amount of radiation, because that level will kill the patient. And my problem is that my programming language isn't agile enough?
- binspace 14y agoYes, because agile methodologies kill people, puppies and hate freedom. Seriously though, in situations where lives are dependent on the solution working correctly, the process that is used to build the solution needs to take into account human error and have rigorous testing. i.e. I also wouldn't trust a person who "though about and can 'prove'" a solution in Haskell to control that radiation machine without extensive testing.
- kibibyte 14y agoAgile isn't right for all software projects. For example, mission critical applications, like medical devices, shouldn't be developed with an agile methodology. Agile is better suited for projects that can be easily and appropriately prototyped.
- philwelch 14y agoExactly my point. For some software, reliability is far more important than agility.
- binspace 14y agoWhy can't you have both? Maybe a different design would become apparent while developing the product, as opposed to being discovered in the analysis phase. (I'm assuming you are talking about a process with a large and separate analysis phase). The worst case is millions of dollars spent to build a product only to discover that there are issues late in the testing phase. Wouldn't is be less risky to experiment and validate assumptions earlier in the cycle? Agile as opposed to methodology X is a bit fuzzy here, as I'm sure testing is extensive and expensive and the feedback cycle is inherently longer, so change is more expensive. However, it seems that early feedback and validation of design is even more important in these circumstances, since changes late in the product development process and orders of magnitude more expensive than changes early in the process.
- philwelch 14y agoYeah, I'm not talking about process so much as languages anyway though. For all I know (I've never actually developed software for a medical device) its worthwhile to build an actual prototype in a more flexible language first. But if my code could kill someone, I want my tools to optimize correctness over flexibility in the final implementation.
- binspace 14y agoAgreed.