News for hackers. Stuff that matters.
Re:Incident Response Documentation by uasm on Monday January 14, 2019 @11:46AM (#18904303)
> "A guide to being on-call... we all have lives which might get in the way of on-call time"

How dare those engineers live a life. They're on-call goddammit.

Re:Incident Response Documentation by lwf on Monday January 14, 2019 @11:56AM (#18904395)
Life gets in the way of scheduled work (on-call).

The section you're quoting is about enabling on-call people to have lives without on-call constraints. It's encouraging people to be considerate and cover a colleague's shift if they want to go out and do something, and you're free.

Re:Incident Response Documentation by sbov on Monday January 14, 2019 @03:19PM (#18906088)
Sure. But scheduling someone for 168 hours in a week means life will get in the way. The way its being phrased though makes it sound like its a privilege rather than a basic fact of life.

Put another way: recognizing this gets you about as many brownie points as recognizing that eating and shitting gets in the way of your average work day. So zero. It's basic logic and human function.

Re:Incident Response Documentation by uasm on Monday January 14, 2019 @12:15PM (#18904531)
> "Life gets in the way of scheduled work (on-call)."

Scheduling 24h work days will inevitably cause "life to get in the way of work". On-calls commonly take a week or two at a time. Stop de-legitimizing work-life seperation.

Re:Incident Response Documentation by lwf on Monday January 14, 2019 @12:53PM (#18904817)
You're reading way more into both the PagerDuty guide and my comments than was intended. Work-life balance is great. Personally, I don't feel like I need to respond to queries on nights or weekends, take plenty of vacation, and feel empowered to push back at anybody going out of those bounds. Then again, I also work at a company where your colleagues will yell at you if you show up on work chat when you're supposed to be on PTO :)

That said, if you're on an on-call shift, and something comes up, that's "life getting in the way". And that's fine.

I have separate issues, personally, with how many companies compensate employees for on-call work. But it is an on-call shift, a concept that exists in basically every industry where you're providing a timely service. (plumbers, airline pilots, systems administration...)

Unless you're large enough to implement follow-the-sun, you're going to need someone to cover the evenings.

Re:Incident Response Documentation by tayo42 on Monday January 14, 2019 @12:24PM (#18904591)
is it possible to work in software and not be on call? it feels like its not
Re:Incident Response Documentation by ultrasaurus on Monday January 14, 2019 @01:16PM (#18905007)
At the end of the day, everyone important is on some kind of defacto on-call (you don't think the head of sales will be woken up for the #1 customer, or the whole marketing team won't be pulled in on a Sunday if there's a big negative story in the NYT?).

A major benefit of PagerDuty is making it explicit how much you're burdening a specific on-call person or team. Some of the new stuff around team health is a great way to show managers "hey, we're pushing unfinished code that's ruining my team's work-life balance, we need to fix our procedures"

(Disclaimer: former PD employee, was on-call for years & learned how to police my work life balance pretty well)

Re:Incident Response Documentation by tayo42 on Monday January 14, 2019 @01:48PM (#18905303)
I get that things happen, even when i made minimum wage and stocked shelves I got asked to work when I wasn't scheduled for an atypical situation.

I guess there's a difference between some once a year oh shit moment and every six weeks planning my life around being close to a computer, phone and an internet connection.

Re:Incident Response Documentation by breakingcups on Friday January 25, 2019 @06:36AM (#18997169)
The company I work for makes and supports bespoke software for a wide range of clients, employing roughly 30 people. We are open from 9-5 and by default provide no support outside those hours. The only exceptions are incidental, well communicated and seen as a logical part of our jobs (for example, a big coordinated release of a new application in the weekend outside business hours).

We host 95% of the applications that we create at our sister company which exclusively does hosting where there is an on-call system, but it is only available to their largest customers and only by request. Of course company-wide alerts (an entire router that goes down, degraded storage, etc.) do garner an on-call response.

Re:Incident Response Documentation by ajford on Monday January 14, 2019 @03:00PM (#18905947)
I worked for a state agency that hosted a data archive and real-time collection of hydrology data. It was not considered "mission critical", and as such there was no on-call.

It was pretty cool, since they practiced 8-hr work days. My only issue was that they were way more focused on ass-in-chair time than productive time, and weren't flexible. At that time, I commuted via bus, and it wasn't uncommon for the bus to be delayed by 15-30 minutes if there were traffic incidents along the route. I wasn't allowed to clock in early if my bus arrived early, and was penalized and documented if the bus was late. So there wasn't a chance in hell I was going to catch the earlier route and arrive 45 minutes before my shift, but they sure were pissy when that bus was late.

Re:Incident Response Documentation by dsfyu404ed on Monday January 14, 2019 @03:33PM (#18906198)
I knew a guy who worked for the local rail transit despots. He used to take their service into work until they told him he had to stop being late and that delays in their own service was not an excuse. At least they weren't in denial about their quality of service.
Re:Incident Response Documentation by fencepost on Monday January 14, 2019 @07:10PM (#18907819)
My passive-aggressive response when faced with something like that was along the lines of "If it's so important that my butt be in the seat at 8 on the dot, then it's equally important that it be walking out the door at 5 on the dot."

Since at the time I was coding in a hallway-facing cube in a cubicle farm, after-hours was my best time to be able to get into "flow" and really get things accomplished without interruption.

Re:Incident Response Documentation by ThrowawayR2 on Monday January 14, 2019 @01:34PM (#18905162)
Sure, just don't work on web sites or services. The jobs are much rarer (desktop apps, embedded systems, etc.) but they're out there.
Re:Incident Response Documentation by wbronitsky on Monday January 14, 2019 @12:53PM (#18904815)
Fortunately for some of us, yes, it is!

After years of being on on-call rotations, including while working at Pager Duty themselves, I am now on a web development team with no pager rotation and no use of paging whatsoever. It all depends on the problem domain you are in, and how the company you work for thinks about supporting and operating their software.

Re:Incident Response Documentation by lytfyre on Monday January 14, 2019 @12:46PM (#18904755)
"Software" might be a bit too broad a brush? Embedded development, or stuff that ships and runs on customer premise don't tend to involve oncall, while SaaS or internal services are more likely to.
Re:Incident Response Documentation by tayo42 on Monday January 14, 2019 @01:45PM (#18905272)
Maybe to broad, but for my question its helpful. I get stuck in the web bubble sometimes and need to be reminded there's more out there.
Re:Incident Response Documentation by chrisseaton on Monday January 14, 2019 @01:17PM (#18905019)
> is it possible to work in software and not be on call? it feels like its not

Yes of course it is. I do research so I don't have any customers yet.

Re:Incident Response Documentation by ams6110 on Monday January 14, 2019 @02:49PM (#18905858)
I do.

We have support during business hours. 9-5, M-F. That's it.