Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In the 1950s, there was the great promise of "the leisure society" - a future of such material abundance that most people would hardly need to work. That society became possible, but we systematically rejected it in favour of more consumption. The cost of living hasn't meaningfully increased, we've just continually redefined luxuries as necessities.

My grandparents are perfectly typical working-class people. They grew up in cramped, damp houses with no central heating or indoor plumbing. They ate mainly seasonal vegetables, considered a chicken or roast of meat a rare treat and often went to bed hungry. They bought new clothes or furniture only when their old ones were beyond repair. They aspired to owning a bicycle, not a car. The only people they knew who had been abroad had done so while in uniform. They didn't regard themselves as materially deprived, because that was the only lifestyle they knew.

As much as we might deny being materialistic, the naked truth is that what we consider to be a basic comfortable lifestyle today was, within living memory, unattainable luxury. We continue to work 40 hour weeks because we have adjusted our expectations to our income. We overwhelmingly choose to work the greatest number of hours we can sustainably tolerate (somewhere between 40 and 60 hours for most people), in order to maximise our spending power.

The recent kerfuffle over "The 1%" is illustrative of this phenomenon. There was widespread mockery of people earning 500k who regarded themselves as just making ends meet. In a very real sense, we are all a part of that laughably oblivious 1%. The lifestyles we consider just about tolerable are, by any historical or global standard, utter luxury. Almost everyone who has ever lived (and almost everyone living today) would consider themselves lucky to have the spending power of an American on minimum wage.



>In the 1950s, there was the great promise of "the leisure society" - a future of such material abundance that most people would hardly need to work. That society became possible, but we systematically rejected it in favour of more consumption.

I'm not convinced this is true: there are also intense coordination costs and learning costs. Two programmers working 20 hours a week, for example, are way less productive than one programmer working 40 hours a week. And the one programmer will learn faster because she's putting in an extra 20 hours a week.

That's true in virtually all knowledge / creative / intellectual professions.

If people are simply executing a set of tasks, maybe working 20 hours a week can make sense, but those jobs are basically commodities, and commodity jobs are a) highly competitive, b) not that remunerative, and c) because of a and b, not that much fun.

EDIT: In response to the commenters below, take a look at Brooks' The Mythical Man Month if you'd like data, at least as far as programmers are concerned.


Sorry, I must disagree. Two people working 20 hours a week are refreshed, not burned out, have time for educationally side projects, etc.

I am in my early 60s and for my whole life I limited my work hours to 32 hours per week, even working for large companies. I had lots of time for educational side projects, exercise, extra time with family and friends, and mediation.

My only regret was not perhaps cutting this to less than 30 hours. I did not work Mondays, and every Tuesday morning I was refreshed and enjoyed my work. Leaving about 20% of my salary on the table was a good trade. Some of my bosses did not like this, but when I worked I gave them 100% effort.


Can I ask how you approached this issue with your employer(s)? I am willing to entertain that trade, but it doesn't appear many employers are willing to even think about it. They might fear it hurts employee relations or is simply too radical to comprehend.


I currently work three days a week for a reasonable salary. Admittedly I live in New Zealand, so possibly the job market is different here (we're a pretty laid-back culture, and there's a shortage of good programmers).

I would suggest negotiating this arrangement when you're changing jobs. Your existing employer will likely be reluctant to reduce your hours, whereas (if you're any good) a new employer will be happy to have you for half of each week if the alternative is not having you at all. And it needs to be clear that that is the alternative. My current employer made me a couple of good full-time offers, which I declined: "I'm currently only looking for part time work, as I need the time to pursue my personal projects and interests."

Still on the theme of "It's better to have you part-time than not at all", you may be able to negotiate an ongoing part-time position at your existing workplace if you are seriously considering leaving (and thus the alternative is your leaving, and their not having you at all). Be careful about this, though. You want to maintain a good relationship. An ultimatum will do you no good. But if you're genuinely in-good-faith considering leaving, they may consider your offer.

You will probably have to try a number of different companies before you find one that will hire you on those terms. And, as with all bargaining, you need to be able to walk away.

DISCLAIMER: This worked for me the one time I tried it, but that may be complete coincidence.


Well, for example, at Google it's possible, some people I know work less than full week, however I doubt that this option is immediately available to a new hire.


That's a very subjective statement. I don't get even remotely burned out by 40 hours of work per week. I work every day of the week. I work when I want to. I don't have a family. I'm 32 years old. The organization of my life is by strict choice, and I love what I do, so I prefer to work longer hours. I'm more productive when I work 40+ hours.

I spend time learning, doing R&D / experimenting, doing product work, etc. The most fun I have is on the R&D. I've been doing it for 17 years straight and there's nothing else I'd rather be doing, I rarely suffer from exhaustion / burnout (and that's always when somethings fails, rather than feeling tired by the actual work).

This discussion is also going to vary dramatically based on the structure of your current life, including family / job / mood / etc. Adding further to the subjectivity of it.


I'm reading the Execute book by Josh Long and Drew Wilson and just last night they hit on the point that a few hours of 100% focused work mixed with a few 100% focused leisure hours a few times a day is more productive and satisfying then say 8 to 10 hours of 45% effort of work.

This is how Drew Wilson, creator of Space Box and many other works is able to achieve his high level of output. He manages his energy, listens to his body and mind, and does what is most suitable and productive knowing such things.

3 hours at 100% followed by 3 hours of leisure followed by 3 hours of 100% work would be 6 hours of 100% focused work. 6 solid hours of work is better than 8 hours of 50% focus (4 hours). Not only is the actual effort put in greater, but so is the focus and engagement which leads to even greater results.


>Sorry, I must disagree. Two people working 20 hours a week are refreshed, not burned out, have time for educationally side projects, etc.

Take a look at Brooks' The Mythical Man Month for data that demonstrates the opposite, at least in programming; I haven't followed the field closely, but education and industrial organization researchers have done similar work in other professions.


Brooks' was at IBM, they adhere to a 37.5 hours per week work schedule. Programmers who can produce 3-4 hours of real work per day are considered productive. Any more and you will start to burn them out.


We stuck to 37 when I was there, so everyone could take off a little early on a Friday.

I mean officially I was there 37, it was a good week if I was doing real, actual work for 20. Yes, I made up for it by working my tail off when it was needed.

We coders can be absurdly productive for short bursts, or be slow and steady. You can't have massively productive and steady for very long. In your early 20s you have a few years of this, but the more you push it then the more jaded you'll be later.


Not to detract from your overall point, but, as an IBMer, I can assure you that - while my full-time employment contract says max 37.5 hours - the reality is that at least 40 hours are expected.


1. That was about 40 years ago when the waterfall process was state of the art. Modern, iterative processes are much more flexible. 2. The loss of productivity levels off as the team size increases. Going from 50 to 100 developers is not the same as 1 to 2.

All said, I expect some loss of productivity is inevitable due to context switching and communication overhead but it isn't necessarily a major loss.


Pretty sure waterfall was never state of the art, rather an example of what not to do [0]. It's often held up as a straw man argument in promoting 'agile'. Brooks' book emphasises prototyping, and 'build one to throw away, you will anyway' which isn't 'waterfall'.

Brooks' book also clearly demonstrates that applying a dumb formula derived from the number of programmers doesn't predict the output, and using such a formula to estimate a project's timeline doesn't positively affect the project's outcome. It's main argument is that programmers added late to a project will actually cause it to take even longer to complete.

Brooks' book is remarkable - a lot of programming lore and culture originates there or is popularized by it. I'd compare it to casablanca or citizen kane rather than dismiss it out of hand.

[0] https://en.wikipedia.org/wiki/Waterfall_development


In software, there is still economy in scale of a person's time. Throwing more people on a project is still detrimental even if you use something like Agile. It is a major loss.

The easy way to combat this is to have longer timelines for projects, or, if necessary, crunch periods followed by more relaxed recharge periods.


Brooks laid out a method as close to assembly line programming as he could, so yes, number of hours you mindlessly follow a formula would affect output. But no one programs like that now and I doubt they ever did. What we do now is closer to writing stories. How many writers do you know who spend a constant 40 hours per week writing for weeks on end?


Err... 20 hours is really not a lot of work.

Some problems, to be solved, require intense work.

At 40 hours a week you will hardly feel "burned out".


It's meaningless to count hours for development work without also talking about how much of that time is spent doing actual work, and their velocity.

Someone who works 40 hours, takes regular breaks and keeps a moderate pace, sure. 40 hours of high pace concentrated development work? In the last 17 years of managing development teams, I've had maybe 1-2 people who could sustain that for more than a week or two at the time.


If it's 20 hours of time-on-task while in flow it's a TREMENDOUS amount of work in a knowledge worker job. We should all be so lucky to be so productive every week.

A lot of people's time is filled by very low-productive work such as excessive communication overhead, or fiddling around with low-quality tooling, etc.


I have some datapoints here. Twice in the last five years I have spent a year working half time (German parental leave is incredible). I noticed spending a higher proportion of my time on 'overhead' - emails, code reviews etc, but my overall productivity did not drop.

I measured the bugs fixed over time, commits made, lines and files changed, emails sent, all proxies for activity.

Some results are shown in this otherwise tangentially related blog post: http://yieldthought.com/post/6070927890/metagame-productivit...

Bear in mind when looking at the charts that they are corrected for man months not calendar months - my calendar productivity remained about the same or slightly better over the measured period.

I recently reduced my hours to 27.5 just by asking. Without these positive experiences for all concerned that may not have been so easy.


>Two programmers working 20 hours a week, for example, are way less productive than one programmer working 40 hours a week.

That makes assumptions efficiency as it relates to number of hours worked that I'm not sure you can make.

How many of those 40 hours are really spent working?

40 hour work weeks are the result of labor regulations, and the binding of health insurance to full-time employment, not a free market equilibrium.


Didn't people work longer back when there were no labor laws?


Yes. It took decades of hard fights, including many that ended up in violent confrontations, to get the working day down from 12+ hours to about 8.

May 1 as an international day of labour demonstration was partly inspired by the immense effort of the US unions at fighting for the 8 hour day, and partly as a commemoration of the Haymarket massacre in Chicago that were part of that struggle:

http://www.illinoislaborhistory.org/haymarket/the-story-of-t...

Even today, there's plenty of people who want to reverse those gains. E.g. in the UK, our sitting PM is trying hard to get additional exemptions for the UK from the EU Working Time Directive because it limits how much extra time employers can demand and/or ask for.


>Two programmers working 20 hours a week, for example, are way less productive than one programmer working 40 hours a week. And the one programmer will learn faster because she's putting in an extra 20 hours a week.

From where did you pull out that data ? It is always possible that one programmer working 20 hours is more productive than two programmers working 40 hours. It depends what they are actually doing.


ceteris paribus


This is best seen through the lens and A type work and B type work. A work is what you get paid for - the delivering value to clients, committing code work. B work is education, design, clearing the desk, sharpening the saw.

40-60 hours a week of A work - or just tryi g to do A work leaves us without B work - soon this piles up into lack of education, lack of preparation.

I would be far better off and more productive if I limited myself to just 5 hours client work a day (or more likely 10 then 0) than the current mad rush.

We need to balance A work, B work and probably A leisure (time with kids) and B leisure ( housework, tv)


Major citation needed. 40 isn't some magical number, it's completely arbitrary. I've never seen a study that found a global optimal number for programming hours per week but if it somehow came out to be 40... that would be a coincidence of galactic proportions.


“The conscious and intelligent manipulation of the organized habits and opinions of the masses is an important element in democratic society. Those who manipulate this unseen mechanism of society constitute an invisible government which is the true ruling power of our country. ...We are governed, our minds are molded, our tastes formed, our ideas suggested, largely by men we have never heard of. This is a logical result of the way in which our democratic society is organized. Vast numbers of human beings must cooperate in this manner if they are to live together as a smoothly functioning society. ...In almost every act of our daily lives, whether in the sphere of politics or business, in our social conduct or our ethical thinking, we are dominated by the relatively small number of persons...who understand the mental processes and social patterns of the masses. It is they who pull the wires which control the public mind.” -- Edward Bernays, 'Propaganda', 1928


If anyone else wants to find out more about Edward Bernays, and how he created the field of public relations, I highly recommend the bbc documentary The Century of the Self. http://en.wikipedia.org/wiki/The_Century_of_the_Self

It is very much in line with the quote that pteredactyl posted. He also did a lot of early work in consumerism and marketing.


> We overwhelmingly choose to work the greatest number of hours we can sustainably tolerate (somewhere between 40 and 60 hours for most people), in order to maximise our spending power.

Not so: http://stats.oecd.org/Index.aspx?DatasetCode=AVE_HRS

(the statistic above excludes vacatyion and national holidays, sick leave, paid maternity/paternity leave etc, which are also much more generous these days)

Note how the well off countries tend to have shorter working hours.

Anecdotally, I only know maybe 2 people who I'd say work more than 40 hours and they're small business owners who really like what they do.


Another data point : the European countries with the longest holidays (France & Germany) are bailing out countries with the shortest holidays ( Greece Ireland Portugal)


Wow, one of those lists that we're at the top position as Turkey, with an almost 50-hour work week (plus 10-15 hours for commuting). I work in a science park inside a university campus and it's mandatory to work at least 45 hours a week. I always thought this is an insanely counter-productive policy and now I have statistical proof.


Are you in Europe or something? In Silicon Valley, 50 hours is a fairly typical week most places I've worked and in some companies much higher numbers are the norm. (edit: and all forms of leave are decreasing rather than increasing)


I believe people who work 40 hours a week are the silent majority, even in tech in SV.


Yes I am. I've heard it's like that with tech in Silicon Valley.


I really wish the US was on that chart!


This one seems to have it, titled "Average annual hours actually worked per worker": http://stats.oecd.org/Index.aspx?DatasetCode=ANHRS


Considering I just spend the last month putting in 80+ hour weeks along with all of my co-workers, might I humbly suggest you put "n=1" after your post? Then again, I work in video games. Long hours are the industry standard.


I hope the 80 hour standard doesn't spread to the rest of the world, lest the games biz loses all the talented workforce with any sense ;)


Most are already leaving.

I was in the industry and left, and I know many that people I worked with have left as well after about 10 years.

In the UK, I might be mistaken as I read the article a while ago, but it is the (or top 5) industry where people spend less time compared to other creative/professional careers.


While I agree with you in general, to some extent poverty/luxury really is relative. If getting a decent job (or starting your own business) means learning how to operate a spreadsheet, then suddenly you're going to need a computer. People didn't have personal computers 50 years ago, but does that make them a luxury now? Likewise, if not having central heating and an indoor toilet makes you a social outcast (who would want to come and visit you in a cold, dark house?) then it stops being about just personal comfort and becomes essential to a happy life.

So, yes, perhaps we don't always have our priorities right (choosing money over time) but it's not necessarily something an individual can do something about -- there's a huge social dimension to it.


"We overwhelmingly choose to work the greatest number of hours we can sustainably tolerate (somewhere between 40 and 60 hours for most people)"

I'm doing that short-term, directly for cash at the moment. Then I'm going to take a month off.

Most of my working life (12 years so far) has been working at the 37 hour mark, mostly because that's what was asked of me at work. There might have been some benefit in working longer hours voluntarily, but I would not have been directly compensated for them and I have a life to live outside of work.

I know this is the privilege of the skilled European tech-worker, and thank god I am one.


My life has exhibited at various points a preponderance of the issues that your grandparents faced. Most people I know still cope with issues mentioned above. I'm not sure why you believe that poverty has vanished even among people on minimum wage: it has absolutely not.


Saying that poverty is significantly and astoundingly reduced is not the same thing as saying it has vanished.


> Saying that poverty is significantly and astoundingly reduced

... is still going to get a lot of people angry, even if you explicitly limit your scope to the First World. It's a combination of lack of historical perspective coupled with a perception that admitting anything has improved is tantamount to agreeing with the people who think social welfare programs need to be eliminated.


Depends on your definition of poverty. Poverty in the sense of the aforementioned grandparents has - only a fraction of a % of the population of the US lacks indoor plumbing.

In the US, people with earned income < $5k/year still tend to consume $23k/year.

ftp://ftp.bls.gov/pub/special.requests/ce/standard/2009/income.txt

By the standards of the past, poverty more or less has vanished. We just raised the bar for poverty so that we have someone to feel sorry for.


We have an organization here in the UK called the Joseph Rowntree Foundation, who lobby on poverty and publish statistics, but they use a relative measure of poverty as basically, being in the bottom third of the population. So, if your next-door neighbours on both sides are watching Blu-ray and you have a lowly DVD player, then they would count you as "living in poverty" for the purposes of the statistics they compile.

When you consider that the very poorest in the UK have free housing, welfare, free education and healthcare, etc, then "poverty" in a global sense is very obviously long since eliminated here.


> Almost everyone who has ever lived (and almost everyone living today) would consider themselves lucky to have the spending power of an American on minimum wage.

And those people you're speaking of live in rural China or sub-Saharan Africa. Someone is not "lucky" by any global standard to be making minimum wage delivering pizzas in NYC or LA.


Oh come on. That person is a bus ride away from some cheaper place, where they can live in comparative comfort.

Its exactly those available resources that separate 1st-world from 3rd-world. We are like fish, who cannot sense the water.


What if that person is a dad who has two kids, a wife, and parents living locally, who take care of their kids during the day? Not everyone can so easily be uprooted.


Yes, that's a difficult choice. Still, they have the choice. They can take the bus, or ride a train, or move in with the parents. Not to mention the free clinic open 24 hours, and the internet, and food stamps, and on and on.

The point is, its a 1st world problem no matter how you cut it. "My job is not satisfying. I wish I had more money for discretionary spending." These are not 'real' problems.


I gotta tell you: not everyone is on the internet. In the US, publicly usable internet usually comes in the form of wifi, or terminals at the library. Not everyone has a library near by. Not everyone has enough money for a cheap cellphone or cheap laptop to take advantage of free wifi. Internet cafes aren't a going concern here.

And some people are legitimately scared of computers! Is it their own problem? Emphatically yes. Is it also society's problem? Again, emphatically yes. Is it their own fault? Well that's a matter of opinion. I think we should solve the problem and then argue over blame if there is time left over.


I suppose nearly all of those reading Hacker News (and the majority of the people in USA) are in the global 2% or so, at least if we measure similarly as here: http://www.globalrichlist.com/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: