3 ms·

ETA: I would assume this is an isolated incident of calling people at 3am until given more evidence to the contrary. Being cognizant of other people's timezone

ETA: I would assume this is an isolated incident of calling people at 3am until given more evidence to the contrary. 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.

Gigachad 4y ago
It’s probably safe to say they didn’t knowingly/intentionally call at 3AM.
- maxbond 4y ago
  ETA: I would assume this is an isolated incident of calling people at 3am until given more evidence to the contrary. 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.
  - lubos 4y ago
    > I'm just saying, being a remote-first company should may you less likely to do this, not more https://en.wikipedia.org/wiki/Faulty_generalization https://en.wikipedia.org/wiki/Faulty_generalization
    - maxbond 4y ago
      ETA: I think I see now, you're thinking that I am suggesting this is a comment on GitLab at large, when it's more likely an isolated incident. I would agree with that. I didn't mean to imply otherwise, but I understand how it came off that way. 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.)
  - Gigachad 4y ago
    A single instance of an employee making a mistake isn’t that interesting imo. If they had a page on their docs which said “call people immediately, regardless of their local timezone” that would be worth discussing.
    - maxbond 4y ago
      I agree it's likely an isolated incident unless we hear evidence to the contrary. Maybe the point I was making wasn't important enough to make, I didn't mean to suggest GitLab was systematically calling people at 3am, but I can see how my comment got swept up in the surrounding discourse and seemed to imply that.

Gigachad 4y ago

It’s probably safe to say they didn’t knowingly/intentionally call at 3AM.

maxbond 4y ago
ETA: I would assume this is an isolated incident of calling people at 3am until given more evidence to the contrary. 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.
- lubos 4y ago
  > I'm just saying, being a remote-first company should may you less likely to do this, not more https://en.wikipedia.org/wiki/Faulty_generalization https://en.wikipedia.org/wiki/Faulty_generalization
  - maxbond 4y ago
    ETA: I think I see now, you're thinking that I am suggesting this is a comment on GitLab at large, when it's more likely an isolated incident. I would agree with that. I didn't mean to imply otherwise, but I understand how it came off that way. 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.)
- Gigachad 4y ago
  A single instance of an employee making a mistake isn’t that interesting imo. If they had a page on their docs which said “call people immediately, regardless of their local timezone” that would be worth discussing.
  - maxbond 4y ago
    I agree it's likely an isolated incident unless we hear evidence to the contrary. Maybe the point I was making wasn't important enough to make, I didn't mean to suggest GitLab was systematically calling people at 3am, but I can see how my comment got swept up in the surrounding discourse and seemed to imply that.