5 ms·
>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 socie
by jseliger 14y ago
>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.
- learc83 14y ago>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.
- sebcat 14y agoDidn't people work longer back when there were no labor laws?
- vidarh 14y agoYes. 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-the-haymarket-affair.html 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.
- mark_l_watson 14y agoSorry, 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.
- jseliger 14y ago>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.
- svachalek 14y ago1. 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.
- seanmcdirmid 14y agoIn 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.
- 14y ago
- 31reasons 14y ago>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.
- reefoctopus 14y agoceteris paribus
- moconnor 14y agoI 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-productivity-boost-stats-and-charts 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.
- lifeisstillgood 14y agoThis 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)
- flyinRyan 14y agoMajor 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.