|
|
|
|
|
by michaelbuckbee
2815 days ago
|
|
This is all anecdata, but I'd describe roughly a third of my past software employees as "crazy" with respect to working hours, etc. The two that really stand out: 1. Enterprise software firm in the healthcare space with a backend lang/storage system that was so antiquated they struggled to find and retain developers. This constraint was so acute that it forced the few remaining developers into a non stop crisis mode as the situation was often "XYZ hospital is down". I left a long time ago, but apparently it's gotten better as they've finally migrated to a more sustainable platform. 2. A hardware/software Augmented Reality startup that had a very difficult time meeting delivery dates. They'd spin up departments like "customer success" and "support" and "technical documentation" and then would have a 6+ month delay shipping. So you'd have very talented people with more or less nothing to do for that timeframe, so people just sat in endless meetings trying to weigh in on everything and it ground the company to a halt. To throw fuel on the fire, they then had the hardware team start working mandatory 6 day weeks (and then made everyone else come in b/c they were "a family"). |
|
A senior to me dev started working nights. I didn't even know he was doing it but I got in trouble for not being there when he was working. Because I "wasn't available when he needed me".