Gave a version of this talk today at PSU. Also referenced http://aphyr.com/posts/282-call-me-maybe-postgres and the four posts following it as a great place for anyone who is now just studying databases, the cloud and failure to explore.
conspiracy to get sysadmins to code, (c) response to how bad software is, (d) recognition of how fast networked software evolves and breaks, (e) all of the above.
T.J. Ostrand and E.J. Weyuker, The Distribution of Faults in a Large Industrial Software System, Proc. Int'l Symp. Software Testing and Analysis, ACM Press, 2002, pp. 55-64.
“because this project can’t be allowed to fail.” - Jim Hightower, http://jimhighsmith.com/2012/01/09/can-do-thinking-makes-risk- management-impossible/
Use a Chatroom: IRC, AIM, bots, logs ✓ Use Voice: Campfire, Skype, VOIP, POTS ✓ Have Headsets! ✓ Designate a time-keeper ✓ Update documentation M aking the change
✓ Designate a note keeper & time keeper ✓ Everyone shares a success, failure, something to do better ✓ Vote anonymously on what to do next ✓ Communicate meeting notes out M aking the change
-by Robert Eberhart, Charles Eesley, Kathleen Eisenhardt January 10, 2012 http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1982819 When you change the institutional expectation for failure, people take more and better risks.
Proven Techniques to Detect Deception, Pam Meyer • Everything is Obvious, Duncan Watts • Ops presentations by Etsy.com • DailyWTF, Full Disclosure, Bruce Schneier