Hacker News new | ask | show | jobs
by crdoconnor 2852 days ago
I've noticed it sometimes ramps up even when management isn't really encouraging it and nobody actually wants to do it.

It's the most straightforward means of signaling relative dedication to the company - Joe the most insecure programmer can attempt to compensate for his skill insecurity by showing more dedication by working longer hours.

That then means that Jane feels implicit, unspoken pressure to work longer because "Joe is doing it". Then this 'arms race' dynamic takes off and eventually it becomes expected and long hours become part of the culture.

It's at its absolute worst when management aren't technical and have to use various "rule of thumb" proxies to determine who is performing well and who isn't, because in the absence of deep technical knowledge guess how they measure you all?

1 comments

I am in that situation right now. Management has decided that a product needs to be rolled out ASAP so some people are working late and weekends. I play an important part in the project but I usually get my stuff done during normal working hours. However, there is a lot of subtle pressure to stay around in case the people working need something. If you are a "team player" you stay.

I don't want to let down others (with whom I have a good relationship) but I also don't want to kill my personal life because management has set an artificial deadline so I have a made a conscious decision to limit overtime only to the times when I actually have something to do.

The overtime cult is an insidious force that's hard to resist. Once a few people start doing it there is a lot of peer pressure on others to do it too. I guess it's a dynamic management can exploit to get more work out of workers by playing them against each other.

Sometimes it's good to lay on the counter social pressure (e.g. "Joe, by staying til 11pm you're making the rest of us look bad. It's not healthy for you and it's not good for us.").