If you're involved in designing critical systems (whatever critical may mean to you and your customers), I can recommend this book for a collection of case studies of where things went wrong: Tragic Design by Shariat and Saucier https://www.amazon.com/Tragic-Design-Impact-Bad-Product/dp/1... If you have an O'Reilly subscription, you can read it on their site.
Check out the recent O'Reilly book Tragic Design for more situations exactly like this. Poor UI design is remarkably common, even on controls that are essential for safe operations. http://www.tragicdesign.com
…discussions on why specific systems have failed and in what ways, particularly where ethics and professional violations can be observed. Classically, the Therac 25 as an example of failure at many levels. See Tragic Design (a recently published O'Reilly book) for cases of bad design leading to tragic or potentially tragic results. A number of them could be turned into case studies in ethics. Examine why security breaches…
Yep. A good book on this sort of thing is Tragic Design [0]. I was in a pilot "Software Safety" course last year and this book was published just after, but was an excellent companion text for the course. I've been meaning to follow up with them to see what…
I can't speak to best practices, but I can to worst. Tragic Design [0] is a text I've recommend to others in the past. It's important to not just know what to do, but also what not to do and why. I haven't reread it since it came out of beta, I read it a few months before…
如果你参与过关键系统的设计（无论你和你的客户如何定义“关键”），我推荐这本书，里面收集了大量系统翻车的案例分析：Shariat 和 Saucier 写的《Tragic Design》https://www.amazon.com/Tragic-Design-Impact-Bad-Product/dp/1... 如果你有 O'Reilly 的订阅，可以直接在他们官网上看。
If you're involved in designing critical systems (whatever critical may mean to you and your customers), I can recommend this book for a collection of case studies of where things went wrong: Tragic Design by Shariat and Saucier https://www.amazon.com/Tragic-Design-Impact-Bad-Product/dp/1... If you have an O'Reilly subscription, you can read it on their site.
我超喜欢《Tragic Design》这本书。https://www.amazon.com/Tragic-Design-Impact-Bad-Product/dp/1...
I really enjoyed Tragic Design. https://www.amazon.com/Tragic-Design-Impact-Bad-Product/dp/1...
去看看 O'Reilly 最近出的那本《Tragic Design》吧，里面全是这种一模一样的情况。差劲的 UI 设计极其普遍，甚至在那些关乎安全操作的控制界面上也屡见不鲜。http://www.tragicdesign.com
Check out the recent O'Reilly book Tragic Design for more situations exactly like this. Poor UI design is remarkably common, even on controls that are essential for safe operations. http://www.tragicdesign.com
……讨论某些系统为什么会失败、以何种形式失败，特别是能体现出伦理和职业操守违规的地方。最经典的当属 Therac-25，作为多层次失败的典范。关于糟糕设计导致悲剧或潜在悲剧后果的案例，可以参考《Tragic Design》（O'Reilly 最近出版的书）。其中不少都可以拿来当伦理学的案例研究。探究为什么会出现安全漏洞……
…discussions on why specific systems have failed and in what ways, particularly where ethics and professional violations can be observed. Classically, the Therac 25 as an example of failure at many levels. See Tragic Design (a recently published O'Reilly book) for cases of bad design leading to tragic or potentially tragic results. A number of them could be turned into case studies in ethics. Examine why security breaches…
没错。讲这类问题的好书有《Tragic Design》[0]。我去年上过一门试点的“软件安全”课程，这本书刚在那之后出版，但拿来做那门课的参考读物简直绝了。我一直打算后续找他们打听打听……
Yep. A good book on this sort of thing is Tragic Design [0]. I was in a pilot "Software Safety" course last year and this book was published just after, but was an excellent companion text for the course. I've been meaning to follow up with them to see what…
我没资格聊什么最佳实践（best practices），但我很懂最烂实践。我以前就向别人推荐过《Tragic Design》[0] 这本书。不仅要知道该做什么，同样重要的是要知道不该做什么以及为什么。自从它出正式版之后我还没重读过，我是几个月前读的 beta 版……
I can't speak to best practices, but I can to worst. Tragic Design [0] is a text I've recommend to others in the past. It's important to not just know what to do, but also what not to do and why. I haven't reread it since it came out of beta, I read it a few months before…