@cyanoacry For a start, risks giving these disasters false connotations:
1) places them mentally in the "primitive past", before we got amazing tools like nodejs and hibernate and such (No, they are more frequent than ever)…
1) places them mentally in the "primitive past", before we got amazing tools like nodejs and hibernate and such (No, they are more frequent than ever)…
@cyanoacry 2) implies they are rare, and when they happen, they gain the stature of, well, the Therac-25 incident
(They are not rare! Many happened in the last hour)
…
(They are not rare! Many happened in the last hour)
…
@cyanoacry 3) implies they are associated with exotic, horribly dangerous equipment such as involving radiation (also misleading. A complex accident might involve seemingly innocuous components)
@cyanoacry 4) Both software and hardware is many orders of magnitude more complex now, and (imho) software engineering has barely evolved, let alone evolved to deal with the increased risks.
@cyanoacry 5) Hyperfocuses on technical issues when social, cultural and ideological issues loom larger than ever. (What do you do when your boss asks you to do something unsafe and/or unethical? What if you can't afford to quit? etc)
@cyanoacry 5a) What if you are working more than 60 hours a week in a safety critical project? What if the company refuses to staff up? What if your manager is making dangerous decisions?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
