3 ms·
Bullshit. When your "minor issue" becomes something that kills people, you test the living bejesus out of it before you think of deploying. When even the slight
by stan_rogers 5y ago
Bullshit. When your "minor issue" becomes something that kills people, you test the living bejesus out of it before you think of deploying. When even the slightest change in UI becomes a deadly operator error, you make damned good and sure that those errors won't happen. There are more things that there is no "undo" (or antidote) for than you can imagine. Having things not isolated is the only real problem.
- midev 5y ago> Bullshit. When your "minor issue" becomes something that kills people, you test the living bejesus out of it before you think of deploying. At no point did I say not to test before rollouts. > When even the slightest change in UI becomes a deadly operator error Stop being dramatic, because it's part of the problem. Yes, UI's are critical, and these UI's are absolute garbage. You need to improve rapidly, not agonize over bullshit changes in Microsoft Office. https://www.thedoctors.com/articles/electronic-health-records-continue-to-lead-to-medical-malpractice-suits/ https://www.thedoctors.com/articles/electronic-health-record... https://ehrintelligence.com/news/diagnostic-medication-errors-rank-among-most-common-ehr-related-issues https://ehrintelligence.com/news/diagnostic-medication-error... EHR's are killing people because they are so poorly built. To reiterate, what you're doing is not working. > you make damned good and sure that those errors won't happen You're not making sure those errors are not happening, is the point.