The dev does have the option of reverting their change.
If significant numbers of devs found the whole process stressful, I wonder if it would help to make the reversion happen automagically after, say, 24 hours, if the dev hasn't committed anything in that time
Devs who have called in sick or over the weekend or attending a wedding or long-planned vacation don't have to think about it.
> The dev does have the option of reverting their change.
Stopping the world seems like an automated process. So should reverting be. In fact, there should be no stopping the world at all, just reverting if the dev can't fix it within 72 hours. There might be cases where automatic reverting doesn't work, but those should still be managed through organizational processes, not by stopping the world.
I'm an unusual American, in that I consider healthy work-life balance to be top priority, at least for everyday employees (founders and such have a different path).
I do try to make room for the idea that my understanding of this is likely superficial, and that there may be things that I am missing, here.
If significant numbers of devs found the whole process stressful, I wonder if it would help to make the reversion happen automagically after, say, 24 hours, if the dev hasn't committed anything in that time
Devs who have called in sick or over the weekend or attending a wedding or long-planned vacation don't have to think about it.