3 ms·
Having worked 70 hour weeks myself, and having worked with Americans doing 70 hours weeks in startups: Outside of very short intervals, I've yet to meet a sing
by vidarh 11y ago
Having worked 70 hour weeks myself, and having worked with Americans doing 70 hours weeks in startups:
Outside of very short intervals, I've yet to meet a single person (myself included) in mentally demanding jobs who actually increase their productivity more than very marginally (in terms of work accomplished in a week) this way. I'm sure exceptions exists, but in 20 years in development and operations work I've yet to meet them.
In fact, I've had to order people to go home and sleep because they measurably increased the defect rates for our code enough to become a net drain.
In other words: I don't just see it as crazy, I see it as inefficient and a quick way to burn out without accomplishing much.
While there may be culture differences involved, the reason I think this is an issue at all is a combination of lack of capturing and reviewing metrics of productivity coupled with a lot of people being delusional about their own work capacity (see the lack of metrics bit) and others being forced to keep up or look lazy in comparison.
I way to often see people having problems getting "enough" work done while being noticeable and obviously slowed down by lack of sleep, for example, only for their response to be to work longer and slow down even more.
- leroy_masochist 11y ago> Outside of very short intervals, I've yet to meet a single person (myself included) in mentally demanding jobs who actually increase their productivity more than very marginally (in terms of work accomplished in a week) this way. I'm sure exceptions exists, but in 20 years in development and operations work I've yet to meet them. I think this rule-of-thumb holds true when you are doing intellectually stimulating, challenging work that requires that you be your "best self". Unfortunately there are a lot of jobs out there, the great majority of jobs in point of fact, where marginal productivity doesn't drop off precipitously past 40 or 60 or even 80 hours. Investment banking comes to mind....
- vidarh 11y agoI don't know any investment bankers, so maybe that's true. Certainly there are jobs that requires little enough of you that you can keep doing the same thing for twice as long. But I'm not convinced that it is "the great majority of jobs". Even in a lot of manual jobs the true cost of reduced attention gets obscured in increased error rates, increased accidents (and according insurance and compensation costs) and burn outs (resulting in higher churn and increased hiring costs). I'm sure some have numbers that prove it's better for them to push staff harder (and places with extremely high salaries like investment banking certainly can take larger productivity drops and still come out ahead than most places), but most places I've worked and most companies I've contracted for, have no clue at all even how to measure their staffs productivity, much less do it on a regular basis. In a few jobs I for the first time (for my managers) started delivering weekly reports that did not just report what we'd done, but combined the reported time spent with average salaries by function and assigned them to products and feature requests etc.. Doing that in my experience always leads to uncomfortable conversations in the team afterwards when management realises what different decisions actually costs. (Amusingly, or depressingly, a common response to me actually asking for average salary information was confusion even when I explained that I was going to report on costs; apparently this is quite unusual for development teams in tech companies to do other than in aggregate for whole departments, which is just plain ridiculous) Generally I take anyone claiming to be just as productive over long hours with a huge amount of salt unless they can explain exactly how they've actually measured it - usually it turns out people are "self reporting" what they think is the case because they feel busier. Often because their productivity has actually suffered, and made them busier.
- xorcist 11y agoWhat's especially bothersome is that the first cognitive function you lose when you're tired and overworked is self-assessment. "This is insane! I've never been so productive" has entered my mind many times just as I looked up, understood that this hour-long work was actually six hours and that meant it wasn't productive at all, and finally went home or to bed. It's only funny in retrospect...
- vidarh 11y agoYeah, I finally beat that by writing a fresh todo list each day with an estimate of how much time I will put in towards each entry today and when I expect to start (rather than how much it will take to complete it). Then I annotate it with when I actually start and stop and notes on why I didn't make my projected start time.... It quickly becomes very sobering reading and quickly made my todo lists drastically shorter to start with, and made me more careful about ensuring I rested enough..