> a lot of programmers don't understand (or don't think about?) what it means to have a failure Most of my devops consulting these days is more on the human si

> a lot of programmers don't understand (or don't think about?) what it means to have a failure Most of my devops consulting these days is more on the human side of things (devs and ops not getting along, Managements Just Don't Understand, etc.) but whenever I end up in a design review this is still the first thing I ask: "how does this break, under what circumstances will it break, and how to we respond to it breaking without waking somebody with SSH access up at two in the morning?".