4 ms·
I had a team a year ago in SV where I had to walk-off the gig for a couple of days. They were putting in 60+ hours a week, sleeping at work. I tried to counse
by DanielBMarkham 8y ago
I had a team a year ago in SV where I had to walk-off the gig for a couple of days.
They were putting in 60+ hours a week, sleeping at work.
I tried to counsel the CEO and CIO, both of whom had been quite successful previously and were determined to "win at all costs" this time around.
They both resisted the procedure.
So I left. I told them that once they came back to being sane again, I'd be happy to come back and help them not do that again, but I wasn't going to hang out and assist them in this insanity.
My guess is that it depends on whether you count by companies or developers. By companies it's probably quite prevalent. By developers? Not so much. But these are the kinds of things companies don't admit to themselves or others. On the flip side of this, there's a ton of apathy in this business as well. Neither extreme is healthy.
- __exit__ 8y agoDid you hear from that team lately in regards of how they're doing? Do they still put in 60+ hours a week or did they switch to a more balanced work life?
- ssijak 8y agoIf company expects 60+ hours per week, and not just in some rare bursts, they will almost never come to senses and scale back to some normal work/life balance. You just need to leave.
- Cthulhu_ 8y agoAnd if there's rare bursts, then someone made a mistake. A lack of planning on your part does not constitute an emergency on mine. Work steady hours, and the "output" becomes predictable (this is what agile methodologies are also about - predictability), which allows for better planning. Working 60+ hours means the output becomes very unpredictable. I mean people will crack and either leave or become overworked at that point, and now there's an even bigger problem.
- deleted 8y ago[deleted]