|
|
|
|
|
by glangdale
2857 days ago
|
|
This is a good way to work. I am hugely skeptical about places that have a culture of crazy long work weeks from a pure productivity standpoint. When we 'rebooted' Sensory Networks (our regex company a while back) we held to a 'regular hours only' policy and I think we did pretty well with it. We did get to a decent acquisition (esp. for a niche product) and importantly we were able to keep progressing the product technically. I suspect that 60-70 hour work weeks lead to a lot of technical debt that will require more 60-70 hour work weeks to pay back. |
|
Except if 60-70 hour workweeks created the debt in the first place, subsequent ones can be expected to create even more, rather than (net) paying any back.
Perhaps a better remedy would be 1.5x-1.75x as many 40 hour workweeks. If so, that could easily be more years than the average engineer's tenure, which can add its own challenge.