GitLab team member here. While it's possible that it could have been 3 AM on Jan... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		john_cogs on Dec 13, 2022 \| parent \| context \| favorite \| on: What I learned at Gitlab that I don't want to forg... GitLab team member here. While it's possible that it could have been 3 AM on Jan 1 in Sydney and midday on Dec 31 in the United States, I think anyone at GitLab, including the recruiter who made the call, would agree that the timing of this call was a mistake - even if the recruiter was within their working hours.

thebricksta on Dec 13, 2022 [–]

It doesn't really matter if it is a mistake; the point is this sort of thing should not happen. Processes should prevent it.

Oops, we lost your data - but don't worry, the team here all agrees that it was a mistake.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact