Hacker News new | ask | show | jobs
by jrockway 2437 days ago
Sometimes I wonder if the underlying issue is that there isn't enough actual work for people to do. I worry that I'm about to sound super out of touch, but hear me out; I'm not making a value judgement about anyone's job.

It is assumed that everyone needs to do exactly 40 hours of work per week, but ask yourself this: for every person in your company, what do their next 40 hours look like? 40 hours worth of HR policies need to be created. 40 hours worth of sales calls need to be made. 40 hours worth of snacks need to be ordered for the office. 40 hours worth of website text updates need to be made. 40 hours worth of UIs need to be designed. 40 hours worth of code needs to be typed in. Isn't it strange that all these vastly different tasks take the same number of hours to complete in a week? My guess is that chattin' is what takes up whatever time remains; people are required to pretend that they do 40 hours of work every week, so they come up with their own way of filling the time. Planning is always valued (and a good idea!), so if you report "yeah I spent the week planning for our Q3 XXX" then it sounds like the money spent on your salary was worth it, and it continues to pay.

As a software engineer, I've never had the problem of not having enough work to do. Tasks are always added to the backlog at a faster rate than they are removed from the backlog. But I feel like a lot of other jobs aren't like this, and the "there is infinite work forever!" thing is most prevalent in fields like engineering, design, art, fabrication, etc.

Meanwhile, most of the people in your average office aren't doing any of those things. To some extent, they're on retainer, waiting for their skills to be needed. And, trying to optimize this is perilous. If you get employee utilization up to 100%, people complain loudly (Amazon fulfillment center workers aren't sending 1000 Slack messages a day). If you try to not pay people for the time periods where they're not being utilized, you just get the "gig economy" which is awful.

I dunno, it all makes very little sense to me. Sometimes I wonder what percentage of the US economy is about doing work that doesn't need to be done, and how many people would not have jobs if we decided "we're not paying for this anymore". I think I'm scared about it, though.

5 comments

Many, if not most, jobs have a peak utilization rate well below 100%. The most obvious example is fire fighting. IIRC, a firefighter should spend less than 10% of their time fighting fires. If they're spending more than that, then they're likely to be busy when you need them.

Sure, they're likely to spend a good chunk of the other 90% working, but it's just busywork. That busywork might be important: they spend a lot of time inspecting and maintaining their fire trucks, for example. But it's not their "real job". Their real job is to be close to the fire truck so that they can respond when an alarm rings.

It's much the same for the rest of us, except that the line is grey, not black and white like it is for firefighters. We have a priority list, and stuff on the bottom of the list will never get done unless it bubbles up in priority for one reason or another. That stuff at the bottom is real work, but since there's always stuff that's more important it's comparable to "washing the fire truck".

And even the stuff at the top of the list is busywork in a way: it's always possible for more important stuff to come in and bump it out of the way. A server can go down, or an important customer can call, or ...

You’ll probably be interested to read about Bullshit Jobs. The authors’ name escapes me currently.
Is it this one, maybe? https://en.wikipedia.org/wiki/Bullshit_Jobs

You're shadow-banned btw (which I normally wouldn't tell) but your comments look OK, so maybe this has happened by accident? You could try to challenge that (maybe via the email support?).

I can see the parent comment, so I think he isn't shadowbanned..?
Comment history is mainly dead, so my guess is they are. Someone likely [vouch]ed for the dead comment in this thread, so it's now visible to everyone.
I vouched.
Fixed now. A rogue spam filter had gotten to them.
I will have to read that. The summary on Wikipedia makes me think the author read my mind.
It should always be "I get paid for giving my employee 40h/ week of availability for work". that doesn't necessarily mean code. there's design, meetings, bugs to find, etc.

ofc, short breaks should be in those paid times. And the hour/week is not the same in every country.

But 40/week doesn't have to be every week, just average (as some times there is less work to do, and other times stuff is on fire and must be fixed)

also, that rate has nothing to do with being remote or on-site.

I find an _average_ of 40 hours to be quite extrem also. I've been at a new 40-hour job for 1 1/2 years now, after working 26/30 hours week for the 3 years prior. My impression is that 30 hours a week might be a realistic average to aim for (26 being the ideal amount IMO). It shifts the work-life balance to "I go to work and in the evenings and on weekends I do whatever I like", where 40 hr / week feels more like "life is work and I'm glad if I get one day completely off on the weekends"

EDIT: Maybe I should give some perspective: I'm single and under the impression that people in a relationship have an easier time managing 40hr weeks because they can better distribute the random shit that comes up every week (how people with kids do it though, I have no idea...). Also I'm currently laying in bed sick, due to having had no reasonable work-week for months, because the only thing I get as reward for finishing my projects in time and to the utmost satisfaction of our customers is even more work. /rant off I guess...

I just said 40h as that is what the law specifies as what is a full time job. Agree that 40h is too much for most knowledge based jobs.
As you optimize a process to get 100% resource utilization, response time for any change gets closer and closer to infinity. You need some slack for things to work, and the more things change, the more slack it requires.

And that's not even considering how humans are physically unable to work 8 hours day in and day out.

There's even a whole book about this: https://www.amazon.com/dp/B004SOVC2Y (by one of the authors of Peopleware[1], which is also excellent).

[1] https://www.amazon.com/Peopleware-Productive-Projects-Tom-De...

I would guess in some positions, like those requiring clearances, that it is more important to have cleared employees there when needed than micromanaging if they are working 40 hours per week.

You wont keep most employees around for part time work, but you want to make sure if your production systems go down or customer orders need to be expedited, or an emergency patch, etc... that you have a team that knows how to do the work, can get it done fast enough and is cleared to do the work (if applicable).

In some cases it might be cheaper to have employees that might be idle a bit than to lose money on downtime. Just a guess though.