4 ms·
> We pulled an ultrahackathon. The team who built this did not sleep much for two days. They worked through Wednesday night, through Thursday, through Thursday
by prima-facie 5mo ago
> We pulled an ultrahackathon. The team who built this did not sleep much for two days. They worked through Wednesday night, through Thursday, through Thursday night, through Friday. They ate at their desks. They wrote the spec late Wednesday evening and they wrote the cutover commit on Friday afternoon, and in between they did the work that the time between those two moments required.
Cool story but I would not want to be in their shoes. Treating your employees poorly only to justify overnight changes in business needs creates a highly toxic work environment.
- deleted 5mo ago[deleted]
- gowld 5mo agoHow much vacation and overtime pay did the team get for that effort?
- rirze 5mo agoForget vacation and overtime pay, I'd expect equity at that point.
- deleted 5mo ago[deleted]
- InsideOutSanta 5mo agoYeah. I understand that this was an exceptional situation outside their control, but having to work multiple days straight is nothing to be proud of. It's something to apologize for and give a corresponding monetary reward for, and then see what kinds of mitigations you can take to avoid this in the future.
- runtime_terror 5mo agoYeah that was a huge red flag. Classic power tripping CEO move to arbitrarily inject a deadline for a new project mid-sprint which then forces your team to work all-nighters and still have them deliver on all their sprint work. If I worked there I'd be immediately looking for a new employer, I guarantee this isn't the first time they've done stuff like this over the years.
- prima-facie 5mo agoThere are cases where the workers' right to stay in the country depends on their employment, in which case this creates a huge power imbalance.
- runtime_terror 4mo agoOh for sure, our H1B visa system is a joke and is just setup for control of labor