[0] https://www.opm.gov/policy-data-oversight/pay-leave/federal-...
Maybe somewhere with a different calendar entrenched might not care so much about Jan 1 though.
https://www.opm.gov/policy-data-oversight/pay-leave/federal-...
It is a 2 week period where fuck all tends to get dome because somebody, somewhere is on PTO or otherwise unavailable.
No.
Being cognizant of other people's timezones/work schedules is an important part of remote work. If you call me at 3am, it'd better be urgent.
Agreed (and the GitLab person in a sibling thread said this as well), but I'm just saying, being a remote-first company should make you less likely to do this, not more. It'd be more understandable to me if they generally hired from a narrow window of timezones and recently expanded to hire from anywhere.
You're saying that I am generalizing too broadly from my experience working remotely? Just linking articles like this is kinda unhelpful, I'd prefer if you stated what your objection was, rather than leaving me to guess and to make your argument for you. That might not be as dramatic as linking an article like a mic drop but it's more productive and prevents misunderstandings.
What I'm saying is that in a remote company (distributed across many timezones anyway), you encounter this situation regularly. So you'd expect the culture of those companies to be prepared for this situation. If I'm missing something in that analysis, I'm happy to be corrected on it.
(I'd point out this was exactly the kind of confusion I was talking about. We had different ideas about what argument I was making, so when I tried to interpret what your criticism was, I guessed wrong.)