Timeline for What should be reported when a bug only happens 50% of the time?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 1, 2017 at 13:58 | comment | added | Peter Mortensen | A more rigorous treatment (pun intended) is in An Investigation of the Therac-25 Accidents (published in IEEE Computer). It is long (four long pages), but interesting, and it should be required reading for anyone involved in functional safety. | |
| Jun 30, 2017 at 20:10 | comment | added | Wildcard | This is so true. If you know precisely what the undesirable behavior is and precisely in what circumstances it happens, your system is still predictable. If you don't know why something is happening, your entire system becomes unpredictable and logical reasoning about it goes out the window because you don't know which of your assumptions are false. From a falsehood anything can be proven. | |
| Jun 30, 2017 at 17:24 | history | edited | Tasos Papastylianou | CC BY-SA 3.0 |
added 241 characters in body
|
| Jun 30, 2017 at 17:15 | review | First posts | |||
| Jun 30, 2017 at 18:20 | |||||
| Jun 30, 2017 at 17:15 | history | answered | Tasos Papastylianou | CC BY-SA 3.0 |