On call this week, so I answered the phone when it rang, because it's my d job, but WHY THE FUCK ARE YOU CALLING ME AT 0410 MY TIME WHEN MY COWORKER IS ON THE CLOCK AT 0710 HIS TIME AND HE'S ABLE TO TAKE THE CALL?! You didn't need me. It was the same issue as yesterday, BUT I DIDN'T FIX A DAMN THING. It resolved itself. The "customer" you had on the phone to work with me to resolve the issue didn't need to be called either, just the application dev. Stop calling people who don't need to be awake just because we were the ones on the call when it self-resolved and none of us know what's going on.

@matsaki95 yes. However, as the primary on call for the week, I have to have my phone on at all times. I was just cranky because:
1. My phone sounds like a fire alarm and an air raid siren had a love child and it scared the daylights out of me (it's new, I forgot about it)
2. I was comfy and sleeping really well for once
3. They *should* have called my coworker first, as his shift started, but they called me instead because it was "easier"

We're on call after business hours, coworker is 3 hours ahead, so he takes the early calls, while other coworker and i take the calls that would run into his dinner time during the business window. He starts at 0400 my time, which was 10 minutes before my phone rang. The people who call us (customers call them, they call us so customers don't have our personal numbers) know this, but it was more convenient to call me apparently.

@matsaki95 I feel bad, my dog had no idea what was going on and started freaking out

@taylorviktorya Assuming you are in the US, you must live near my side - I'm in AZ, where the time difference is even more confusing since we don't observe DST, so depending on the time of year, I'm either 2 or 3 hours behind ET.

I get called, emailed and instant-messaged at the most bizarre times (especially since I work with overseas associates as well) - and no one ever knows / understands what time it is where I live.

Sometimes I use it to my advantage and get out of a useless meeting by claiming "sorry, timezone conflict.."; but usually it's just a royal PITA.

I used to look suspiciously at self-resolving issues, knowing they are likely to just "re-appear" - but as time goes on, I've become very comfortable blaming problems on "transient cosmic ray parity bit misalignment" and just moving on to something else...

Jaded or just exhausted, I'll take it.

@cdrice very much this. I'm pdt. I can't get away with timezone conflicts. I just tell people that I'm intimidating and make it work by joining the call or something equally corny. They laugh and hang up and don't yell about how I'm taking too long to fix things.