Live data from Hacker News

Breaking Up with On-Call

reflector.dev

201–202 of 202 posts

Re: Breaking Up with On-Call

#201

Earlier quoted context omitted.

You have conflated two arguments: 1. That it's harmful 2. That it's easy to do something else (1) is the important point, (2) is irrelevant. On the important point, you seem to have assumed several things: a) that it is harmful b) that anyone to whom the assumed harm would occur would see it c) that they would know what the camp looked like (a) I see no evidence for this, in fact, research suggests the opposite[1] >…

Wow, it's really important to you to have a picture of a concentration camp guard tower up.

More important than that to me is the use of rational, sound, valid reasoning, and the avoidance of petty and facile straw man arguments.

But okay, I really want there to be a picture of a concentration camp guard tower, because the best way to deal with childishness and unreasonableness is, unsurprisingly, childishness and unreasonableness.

Re: Breaking Up with On-Call

#202

Earlier quoted context omitted.

Devs need to be on call at three AM so that they suffer when their software fails. This is how you align developer motivation with operational motivation. The organization needs to incur financial penalties when the on-call staff have to respond at three AM. This aligns the organizations motivations with the operational motivations. When managers see an on-call-incident line-item going up then they're more willing to…

> Devs need to be on call at three AM so that they suffer when their software fails. This is how you align developer motivation with operational motivation. As I mentioned in a peer response: Punitive management policies erode morale and result in retention only of those whom have no better options. See "Price's Law"[0]. 0 - https://nielsbohrmann.com/prices-law/

It's interesting that you see this as being a punitive policy. Our job is producing quality systems. If our software is so bug ridden that caring for it is a punishment, then failed we've at producing quality software.
Post reply on HN