I work on-call. Even if it is supposed to be someone else's day I get called more often than not.
I don't complain and I get the job done. That is what the point is. I don't like it but I sleep like crap anyway so if it wakes me up I may as well go get to work.
Before I was able to be remote I had the same issue for decades. I was in-office 5+ days a week (it depended on the work needing done) AND I was 24/7 on-call. Nothing like running hundred hour weeks to burn you out.
However, I just function like this now. I don't like it. It impacts the rest of my life (but less now since I am not 24/7 all of the time).
Since I am remote, I can hour-shift without having to worry about a commute and being too tired to safely drive. Believe it or not, I am pretty damn safe messing will tens of millions of dollars of infrastructure tired than I am behind the wheel after a shitty night of on-call work.
Bonus? I can take a break for a bit, have someone cover me and get a power nap in and get back to functional-ish for the rest of the day. That is a LOT harder when you have a commute to think about or could have some shit come up at the end of the day and your already 12 hour day turns into an 18 hour day (and you still need an hour to drive home).
Archive: https://archive.today/xU46f
From the post:
>In the last 3 years I've attended 77 meetings that began between 1am and 6am, roughly once every two weeks, followed by my usual 7am start, Monday to Saturday. I'm working remotely from Australia for a US firm (Intel) who does not have a local office here. I'm not complaining. I work weird hours, but I don't think I work too many. I'm writing this post because there are some misconceptions and assumptions about the lives of remote workers, and I thought I'd share my own details as an anecdote, along with some tips for others in a similar situation (US job from Asia).
I work on-call. Even if it is supposed to be someone else's day I get called more often than not.
I don't complain and I get the job done. That is what the point is. I don't like it but I sleep like crap anyway so if it wakes me up I may as well go get to work.
Before I was able to be remote I had the same issue for decades. I was in-office 5+ days a week (it depended on the work needing done) AND I was 24/7 on-call. Nothing like running hundred hour weeks to burn you out.
However, I just function like this now. I don't like it. It impacts the rest of my life (but less now since I am not 24/7 all of the time).
Since I am remote, I can hour-shift without having to worry about a commute and being too tired to safely drive. Believe it or not, I am pretty damn safe messing will tens of millions of dollars of infrastructure tired than I am behind the wheel after a shitty night of on-call work.
Bonus? I can take a break for a bit, have someone cover me and get a power nap in and get back to functional-ish for the rest of the day. That is a LOT harder when you have a commute to think about or could have some shit come up at the end of the day and your already 12 hour day turns into an 18 hour day (and you still need an hour to drive home).
Archive: https://archive.today/xU46f
From the post:
>>In the last 3 years I've attended 77 meetings that began between 1am and 6am, roughly once every two weeks, followed by my usual 7am start, Monday to Saturday. I'm working remotely from Australia for a US firm (Intel) who does not have a local office here. I'm not complaining. I work weird hours, but I don't think I work too many. I'm writing this post because there are some misconceptions and assumptions about the lives of remote workers, and I thought I'd share my own details as an anecdote, along with some tips for others in a similar situation (US job from Asia).
