4 ms·

It’s Christmas Eve, I aint answering any PagerDuty notification today or tomorrow.

by altdataseller 5y ago

voidfunc 5y ago
- Macha 5y ago
  Yes, they'll understand if the impact is worth paying someone(s) for 24/7/365 support, and so far they've decided the answer is no. In my company's industry, it probably is correct - our customers don't work christmas eve/day either. At my previous company they did - and so oncall and its compensation was specified in the contract and there was a formal rota.
  - geofft 5y ago
    Also, quite literally, people (both management and other engineers) often don't fully think through the consequences of systems that have neither enough automatic failover nor enough staffing by non-distracted humans, and build systems assuming that it will be fine. It's probably better to suffer an unexpected outage now than in the future when your company is bigger.
  - aaomidi 5y ago
    It's funny, SREs and SDEs generally get paid around the same in most places. I know some companies compensate oncall time differently, but a lot don't. SREs work a loooot more hours than SDEs, and I feel like that's partly on SREs for just accepting that workload. In my current position, if I get woken up at night even once, I take that as 8 hours worked and take a whole day off. The other side of offering "unlimited time off" :). This creates a real cost on technical debt, and forces actually addressing them rather than letting human capital deal w/ them.
    - lumost 5y ago
      Curiously this made my transition from SRE to SDE somewhat interesting. After I transitioned I kept working the same hours I would as an SRE and would be surprised at the lack of output from my coworkers. It wasn't until later that I realized it was simply the difference in hours worked. As an SRE, your only option for climbing out of the mess is to work harder/smarter/extra, and you are always lowest on the totem pole when messes happen. You either learn to keep up with the crazy schedules, or get the hell out of dodge.
      - aaomidi 5y ago
        I actually transitioned from SDE to SRE, and you can imagine how awful it was for me doing the opposite. SREs are the hardest working engineers I know, but unfortunately they're not given a lot of autonomy to fix problems. Or one SREs has strong opinions about stuff and blocks fixing things. My conclusion has been that everyone needs to be devops. SDE needs to also own the ops of the thing they've developed.
        dvtrn 5y ago
        My conclusion has been that everyone needs to be devops I used to think this way. But time and time again I found that organizations treated Devops and SRE as either "developer help desk" or "hiring some person to do terraform stuff and calling them the 'DevOps Team'" or "we literally failed to hire actual technical specialists for the role we needed, so we're just going to dump these tasks on the Devops 'team'" I no longer think the way I used to about Devops, I also no longer have any real interest in being part of 'Devops transformation' efforts. Go figure.
        dragonwriter 5y ago
        > My conclusion has been that everyone needs to be devops DevOps wasn't conceived as a new and additional role or org, but as a model, and a model whose main point was eliminating inefficiencies resulting from role/org/knowledge/responsibility separations between dev and ops. Creating a new role, often in its own sub organization, as a distinct knowledge and responsibility silo for “DevOps" is like management instituting a rigid top-down development model without dev team ownership and control or customer participation and calling it “Agile”: Completely missing the point and also exactly how most places do it.
  - 5e92cb50239222b 5y ago
    >rota I apologize for offtop, but are you British? I have only seen this word in the British literature and now I'm wondering if Americans or Canadians or Australians ever use it.
    - Kye 5y ago
      US here and I've never heard the word. I thought it might be an acronym until I read your comment.
    - reallydontask 5y ago
      What do you call a rota? Seems a word in common use in the UK
      - eropple 5y ago
        "Rotation", in the US. I've never heard "rota" as shorthand before. That's interesting!
      - toyg 5y ago
        I guess they use something like "duty" or "shift plan". Rota is indeed very British. It clearly comes from the Latin word for "wheel", but in Italy it is not used (nor in France, afaik) - we have the Sacra Rota (which is the Catholic ecclesiastical tribunal, typically invoked for marriage dissolutions) and the word rotazione which is "rotation" and can indeed be used to indicate shift planning. Now I wonder if "rota" in that context comes as a shortening of rotation...
      - kiwijamo 5y ago
        Here in New Zealand we usually use 'roster'.
    - Macha 5y ago
      Nope, Irish
- aaomidi 5y ago
  They can go and respond if something is that important. Oh, wait, what's that? They don't know how to? Interesting, they seem to be getting paid a shit ton more than the engineers keeping everything running.
  - lumost 5y ago
    by and large managers are only paid 10% extra. This 10% is applied at the band level, it's incredibly common for the engineers working for a manager to make more than they do.
    - aaomidi 5y ago
      It really depends on the org I think. But Boss's Boss probably gets paid 40-50% more.
- peakaboo 5y ago
  Does the boss pay?
- ohgodplsno 5y ago
  Imagine thinking your boss's business is more important than taking time off with your family (or alone) on Christmas.
  - voidfunc 5y ago
    /r/antiwork is leaking into HN I see. I'm paid to keep the lights on as well as build new lights and light features. Maybe you aren't, but if you're on an on-call rotation my guess is you probably are and are expected to respond to incidents if they arise regardless of what day it is.
    - ohgodplsno 5y ago
      Please, antiwork is too recent for my tastes, I've been shitting on my bosses for a decade now. I've been on call too. And nothing is worth dropping the one time your family might actually be together during the year to fix a damn server going down. My bosses make a dollar and give me a cent on that while expecting me to be on call? Fuck them.
- omginternets 5y ago
  Man there’s always someone to suck up to the boss, even when it’s not his own. I really struggle to understand what this moralizing is meant to achieve.
gumby 5y ago
If pager duty uses aws you won’t have a problem
- pmarreck 5y ago
  DNSception!
tyingq 5y ago
You could just borrow the AWS wording. Say that you're answering the on-call pager, but with "elevated latency".
- Krisjohn 5y ago
  Yoink
  - Shorn 5y ago
    Succinct. Yoink.
- Shorn 5y ago
  "My standard Service Level Agreement for on-call is an average incident response time of < 24 hours (including weekends). Leave requirements may see periods of elevated response times." In other words, I'll start to work on your problem at 0800 local time the next work day.

It’s Christmas Eve, I aint answering any PagerDuty notification today or tomorrow.

voidfunc 5y ago

Macha 5y ago
Yes, they'll understand if the impact is worth paying someone(s) for 24/7/365 support, and so far they've decided the answer is no. In my company's industry, it probably is correct - our customers don't work christmas eve/day either. At my previous company they did - and so oncall and its compensation was specified in the contract and there was a formal rota.
- geofft 5y ago
  Also, quite literally, people (both management and other engineers) often don't fully think through the consequences of systems that have neither enough automatic failover nor enough staffing by non-distracted humans, and build systems assuming that it will be fine. It's probably better to suffer an unexpected outage now than in the future when your company is bigger.
- aaomidi 5y ago
  It's funny, SREs and SDEs generally get paid around the same in most places. I know some companies compensate oncall time differently, but a lot don't. SREs work a loooot more hours than SDEs, and I feel like that's partly on SREs for just accepting that workload. In my current position, if I get woken up at night even once, I take that as 8 hours worked and take a whole day off. The other side of offering "unlimited time off" :). This creates a real cost on technical debt, and forces actually addressing them rather than letting human capital deal w/ them.
  - lumost 5y ago
    Curiously this made my transition from SRE to SDE somewhat interesting. After I transitioned I kept working the same hours I would as an SRE and would be surprised at the lack of output from my coworkers. It wasn't until later that I realized it was simply the difference in hours worked. As an SRE, your only option for climbing out of the mess is to work harder/smarter/extra, and you are always lowest on the totem pole when messes happen. You either learn to keep up with the crazy schedules, or get the hell out of dodge.
    - aaomidi 5y ago
      I actually transitioned from SDE to SRE, and you can imagine how awful it was for me doing the opposite. SREs are the hardest working engineers I know, but unfortunately they're not given a lot of autonomy to fix problems. Or one SREs has strong opinions about stuff and blocks fixing things. My conclusion has been that everyone needs to be devops. SDE needs to also own the ops of the thing they've developed.
      - dvtrn 5y ago
        My conclusion has been that everyone needs to be devops I used to think this way. But time and time again I found that organizations treated Devops and SRE as either "developer help desk" or "hiring some person to do terraform stuff and calling them the 'DevOps Team'" or "we literally failed to hire actual technical specialists for the role we needed, so we're just going to dump these tasks on the Devops 'team'" I no longer think the way I used to about Devops, I also no longer have any real interest in being part of 'Devops transformation' efforts. Go figure.
      - dragonwriter 5y ago
        > My conclusion has been that everyone needs to be devops DevOps wasn't conceived as a new and additional role or org, but as a model, and a model whose main point was eliminating inefficiencies resulting from role/org/knowledge/responsibility separations between dev and ops. Creating a new role, often in its own sub organization, as a distinct knowledge and responsibility silo for “DevOps" is like management instituting a rigid top-down development model without dev team ownership and control or customer participation and calling it “Agile”: Completely missing the point and also exactly how most places do it.
- 5e92cb50239222b 5y ago
  >rota I apologize for offtop, but are you British? I have only seen this word in the British literature and now I'm wondering if Americans or Canadians or Australians ever use it.
  - Kye 5y ago
    US here and I've never heard the word. I thought it might be an acronym until I read your comment.
  - reallydontask 5y ago
    What do you call a rota? Seems a word in common use in the UK
    - eropple 5y ago
      "Rotation", in the US. I've never heard "rota" as shorthand before. That's interesting!
    - toyg 5y ago
      I guess they use something like "duty" or "shift plan". Rota is indeed very British. It clearly comes from the Latin word for "wheel", but in Italy it is not used (nor in France, afaik) - we have the Sacra Rota (which is the Catholic ecclesiastical tribunal, typically invoked for marriage dissolutions) and the word rotazione which is "rotation" and can indeed be used to indicate shift planning. Now I wonder if "rota" in that context comes as a shortening of rotation...
    - kiwijamo 5y ago
      Here in New Zealand we usually use 'roster'.
  - Macha 5y ago
    Nope, Irish
aaomidi 5y ago
They can go and respond if something is that important. Oh, wait, what's that? They don't know how to? Interesting, they seem to be getting paid a shit ton more than the engineers keeping everything running.
- lumost 5y ago
  by and large managers are only paid 10% extra. This 10% is applied at the band level, it's incredibly common for the engineers working for a manager to make more than they do.
  - aaomidi 5y ago
    It really depends on the org I think. But Boss's Boss probably gets paid 40-50% more.
peakaboo 5y ago
Does the boss pay?
ohgodplsno 5y ago
Imagine thinking your boss's business is more important than taking time off with your family (or alone) on Christmas.
- voidfunc 5y ago
  /r/antiwork is leaking into HN I see. I'm paid to keep the lights on as well as build new lights and light features. Maybe you aren't, but if you're on an on-call rotation my guess is you probably are and are expected to respond to incidents if they arise regardless of what day it is.
  - ohgodplsno 5y ago
    Please, antiwork is too recent for my tastes, I've been shitting on my bosses for a decade now. I've been on call too. And nothing is worth dropping the one time your family might actually be together during the year to fix a damn server going down. My bosses make a dollar and give me a cent on that while expecting me to be on call? Fuck them.
omginternets 5y ago
Man there’s always someone to suck up to the boss, even when it’s not his own. I really struggle to understand what this moralizing is meant to achieve.

gumby 5y ago

If pager duty uses aws you won’t have a problem

pmarreck 5y ago
DNSception!

tyingq 5y ago

You could just borrow the AWS wording. Say that you're answering the on-call pager, but with "elevated latency".

Krisjohn 5y ago
Yoink
- Shorn 5y ago
  Succinct. Yoink.
Shorn 5y ago
"My standard Service Level Agreement for on-call is an average incident response time of < 24 hours (including weekends). Leave requirements may see periods of elevated response times." In other words, I'll start to work on your problem at 0800 local time the next work day.