IMO the need isn't for 6 hour workdays but for some regular outside of work time available during the work week.
I work an 8:30-5:30 job and this ensures that everything I need to do outside of work during normal business hours builds up to consume my weekend. I know several people who work for business with half-day Fridays and that's when they get all of their outside-of-work things done ensuring that their weekends are actually free for doing the things that they want to do.
If you have kids this is an even bigger deal. If you don't, you're free for whatever every evening. If you have kids, your after work time is committed until they get to sleep every night. Having that work-day time when your kids are in school becomes HUUUUUUUGE.
I also know people who work for CVS doing 12 hour shifts with a limit of 80 hours over the course of two weeks. This leads to a lot of full days off every 2 week period...and they love it.
It's less about the "X hour workday" and more about the "X hours of free time during regular working hours"
I had nearly the opposite of this in Japan where even leaving the office premises was a hassle and required manager approval (security gates at every entrance logging your movement -- this was after a security breach where an employee stole 30,000 design documents and became a national headline).
As you might imagine his was terrible and required you to Often use PTO just to go to the bank or the municipal office for some registration work. Also it just makes you feel less than human when you're controlled so thoroughly.
I've worked a half-day Friday schedule (in a factory situation where productivity is much more easily measured) and while the hours were _great_ for the workers, it played havoc with productivity and output. Most people basically slowed way down on Fridays because they knew that a) there wasn't much time to do anything so why not wait b) everyone else was slow so it would take even longer. Ideally in this situation, you would get more out of your workers on Mo-Thu but that didn't happen.
Instead, they went with a 9/80 schedule and it worked out great for management and the workforce.
“A "9/80 schedule" means that on 4 days per week you work 9 hours, and on the 5th you either work 8 hours or you have a day off. So for example, you may work 9-hour days Monday through Thursday, and on Fridays, you either work an 8-hour day or take the day off. 9/80 means that you work 80 hours over 9 days, instead of the traditional 10.”
I suspect this is a little confusing to any day care that doesn't also operate 9/80. I did 4/10s for my kids entire day care "career" and that was enough to really confuse them a couple times.
Another fun day care problem is some bill by week and make the employees watch the clock like hawks to make sure no one is getting more than their fair share, while others bill by the hour and don't care if you're late, in fact they enjoy the extra money. Both sides sometimes insist the other side doesn't exist and their way is the only correct way to run a day care. Obviously 9/80 or 4/40 or anything more exotic than 9-5 M-F is going to need some care in selecting the correct day care billing model
(Note strange, yet honestly serious possible startup topic: brokering parents with day cares WRT weird schedule constraints and location constraints)
I think it's partly that a lot of 8-hour-day jobs bleed towards 9 hours, but (explicit) 9 hour days are less likely to bleed up to 10. But even at stated hours, it's got a lot of advantages. Free weekdays are incredibly useful, and the ability to schedule around 3 day weekends (or 4 day weekends on holidays) is a huge hit with people who want to take any kind of short trips.
Swedes typically do 9h days because we take long, unpaid lunches. White collar workers in cities normally do ah hour at noon -1pm. The 9h day is a bummer, but with flexible hours at least I can normally do a 2h lunch if I need to go to the dentist or sort something else out.
Half days off is a brilliant idea, because it makes it easy to know when to schedule kids appointments withe doctor etc.
No, an 8h workday excludes lunch, so typical hours in Sweden are 7-16 or 8-17. If I take a 2h lunch I might work 8-18. There is no such thing as 8-5 that makes no sense in Sweden :)
Interestingly, while lunch isn't counted towards the 8h, the workday normally does allow for coffee breaks ("fika") on paid time totaling 15-60minutes depending on what business.
I think it depends on the trade. I'm in the process of leaving a IT job that forces you to take a unpaid "lunch" but expects you to be available to them during that time. Its a way to cheat and fill the schedule in some cases.
The latter is perfectly reasonable in some (many?) circumstances.
Break-fix work needing to be done on-call/24x7 while requiring in-office presence for design and new feature development (a fundamentally different type of work, typically requiring a higher level of collaboration) seems perfectly reasonable to me.
> The latter is perfectly reasonable in some (many?) circumstances.
I live in a northern climate and when it snows can either spend 1 hour stuck in traffic or just work from home (and possibly come in after traffic has cleared).
My previous employer was adamant about being in the building from 0830 to 1700 even if it was a blizzard. My current employer lets the employees manage whether they need to come in or not (any day not just during bad weather). I'm sure you can guess which one has happier and more productive employees!
I'm facing a Nor'easter, 12+" of snow, etc, here tomorrow and will be working from home for the day. To me, that's perfectly natural and anything less flexible would be insanity/inanity.
The key there is (almost) no one will be in the office because it's a synchronized event. OTOH, if everyone worked from home 2x/week at random, it would be chaos trying to plan whiteboard design sessions.
Either I'm working and then I'm paid and available. Or I'm not working e.g on lunch in which case I might be available if it's urgent. If I do tend to something on my lunch (being nice) then obviously I'm working again - so I'll just go home early instead. Obviously I'm only available on lunch if I can, and want to.
It's hard to fit into a schedule with picking up kids from School though. In parts of Germany and Switzerland where that is still the norm I think it's at least partially a leftover from a time when women did that - so not very modern. A friend who worked in Germany and left to pick up kids at 5pm was sought by the manager and when he heard my friend had left to pick up kids he said "doesn't he have a wife?". Pretty traditional...
But an hour lunch is great to have lunch with your kids, something both my parents still did with my and my brother.
My kids' school only switched to a schedule where the kids eat at school two years ago, and I have a job in another city. But it was something quite a few parents managed to do until then.
When the kids don't eat school where do they eat (assuming most kids have two working parents who commute away from where they live every day)?
I saw that system in some old fashioned societies (e.g Switzerland) and while it seemed good for the kids, it seemed to mean a lot of women staid home to feed kids rather than work (if they couldn't afford a nanny that is).
I think school lunches are pretty essential for getting a high workforce participation for both men and women.
First of all, kids in Switzerland typically don't get picked up, they're supposed to go home and to school by themselves from 6y on. At least one parent usually works nearby the home and can take a 1.5 to 2h lunch break, that leaves enough to prepare and have everyone eating at the table at the same time for 30min - traditionally the whole family with both parents. A more modern version of this is to share the task friendly neighbours with same age kids, so a few days of the the week the kids eat at neighbours' houses.
In any case, lunch time is kind of a sanctuary here - deskside lunches are seen as very poor - even if people stay at work they'll go to an affordable restaurant together. I can say that this has lots of advantages, an actual real break from work really does recharge your batteries. Swiss workers are usually measures among the most productive per hour worked, and IMO a full lunch break is necessary to achieve that.
Edit: Btw women in workforce participation is 62% compared to 56% in the US, 54% in Germany and 60% in Sweden.
Yeah deskside lunches is unheard of in Sweden as well, and kids I think are about as expected to walk alone here (It's getting worse than it was when I grew up, but that I believe is pretty universal across europe and elsewhere) but having to switch jobs to work close enough to home sounds almost impossible in big cities. Those with short commutes might have 20-30 minutes, but more typical commutes in cities are 45 minutes. That's 90 minutes there and back. I'd rather just get my workday over with in 40-90 minutes less than go home to have lunch, and I don't want 4 commutes in one day (even two is too much).
Spending two hours or more on lunch would be great, but I also want to eat no later than 6 (kids go to bed 7!) so it's very hard to squeeze in with two full time jobs of 8h.
I think the system is a nice idea in theory when you have great neighbors or walking distance to work - but the probability that this is the case for a whole school class is slim. I think it feels a bit like a remnant of a housewife society and something that adds pressure for parents to stop working - which isn't a bad idea per se but it tends to add more pressure on women to do so.
Swiss cities have a separate public system where your children can go for lunch and even dinner though. Good public transport is another thing, commutes typically are 10-30min even in Zurich, so even city workers can often afford to go home. Anyways, there are ways to solve this without having lunches provided for every schoolchild. The quotes workforce participation quota shows that for a majority this is at least doable.
Well there is a service you can pay for where your kids have lunch at school and are under supervision, but it was opt-in.
Now the class eats with the teacher in half an hour and there is no option to eat at hone anymore. School finishes half an hour earlier so the commuting parents still have to pay for child care.
One of the problems was that there aren't many good people available for the job of child care for one hour at lunch time, people leave when they find something better.
More good reasons not to bother having kids. Just too much hassle; our employers and governments are doing everything they can to make raising kids a miserable chore, so why bother?
You work 40 hour weeks in Sweden? No wonder so many Swedes want to work in Norway. A lot of people's working days here are 8 hours including a half hour lunch break, 37.5 hours work a week. I generally start at 07:30 and finish at 15:30.
Of course as a salaried employee I have quite a lot of freedom to set my own hours so I sometimes work an extra half hour so that I can go home early on Friday or have some hours I can use to get things done without having to use a holiday day.
While I think fewer working hours are need overall, you are right about needing time during the work week. For example, contactors, who seem to only work during the week despite the majority of their customers having day jobs, would be a lot easier to work with if one doesn't need to use a half or full day for them.
I'm fortunate in that if I need to take time to deal with that or work from home I can, but I'd assume most can't do that easily.
The other thing I can't help but fixate on is that this consumption of all free time seems to nicely reduce the risk of employees starting their own business or even look for another job. Much harder to do those when you're exhausted or dealing with family.
The last place I worked at they did 4x10 week where you work 40 hours in 4 days and then have Fridays completely free. My manager adjusted it so that half the team was 4x10 for two weeks and then the other half of the team was 5x8 so there were no days where the whole team was out of the office.
It worked out pretty well, but there were some obvious flaws like someone dropping the ball a few times here and there and the rules got changed where you had to have "availability" on your day off, just in case someone had a question, or something broke that you checked in.
> If you don't, you're free for whatever every evening.
Sometimes a lot of "house chore"-y stuff requires going to places that are closed after you get home. Unless you have flexible-ish work start time (which many tech companies do), you're doing that on the weekend or waking up earlier.
Banks, most contractor/consulting stuff like dealing with a CPA or lawyer, anything medical, even just shopping at specialty stores. I remember my parents changed banks when they both returned to work because only one local bank stayed open past 5.
Having a block of "standard work time" for asynchronous tasks (e.g. writing code, building a car) makes sense, but having it collide with the schedule of e.g. buying insurance is really weird to me.
I like your CVS point. I have always thought if I could work 4 ten hour days instead of 5 eight hour days I would be much happier. I don't mind long working days and it is not often that I only work an 8 hour day, but if I got an extra full day off in exchange for those extra hours that would be ideal.
Mexican billionaire Carlos Slim has a similar plan - he says we should all work just three 11 hour days per week (and change the retirement age to 75).
I think that, at least for jobs that require significant context-building spinup time at the beginning of a work period before you can start producing useful work, this is a great idea.
Normally anything billionaires advocate in changing society is horrible, but in this case I have to agree heartily. Working only 3 long days a week would work out great for me. That would give me 4 full days off, plus as a programmer there's a significant amount of "spinup time" as you put it; this just isn't the kind of work you can work on in short bursts.
However, I think the 6-hour day plan has some real merit too. I think it just depends on the job. For an engineering or programming job, I think the 11-hour day makes a lot of sense. But for some job like nursing (as in the article), or customer-service jobs where you're running around the whole shift, I think the 6-hour day (5 days a week) makes a lot of sense so workers don't get too worn out.
There was one great point in this article: setting society-wide hour counts is probably a bad plan.
11 hour days sound delightful for a lot of jobs - lots of productive time at work, with enough time off to relax and travel. They also sound hellish for some work (11 hours of manual labor is wretched) and impractical for some (11 hours waiting tables misses prime hours).
So I think that conditional is important, but it sounds like a great thing to offer where possible. I can certainly see taking it as an occasional or even permanent schedule.
That's very interesting. I wonder if you would start to run into staffing issues with this. Especially in industries like healthcare where it is already difficult to find adequate numbers of staff in certain roles like nursing.
I've known a few people working 4/10 schedules (four days, ten hours), but I think managers are often skeptical that an employee is still fully efficient 10 hours in. I know more people working 9/80 (nine hour days, alternating 4 and 5 day weeks), which is less exhausting and still allows for free days and convenient 3 day weekends.
That's probably a fair criticism, but how many people are still fully efficient 8 hours in? I think as an employer you have to accept that you are going to be getting some hours out of your employees that are not fully productive, and ask yourself if getting some productivity during those hours is better than getting none.
9/80 sounds like a good tradeoff. I had never heard of it before this thread. That's why I love HN. It's better than /r/todayilearned/
Could not agree mofe, here in I dia every stupid Govt thing requires your presence despite the "digital India" push, that too alternate working Saturdays! And on that satirday they ask you to come on Monday. There is really a need to give friday half day or something like that
Related to that, why aren't public servants at the DMV, utilities, etc., required to work on weekends and have their days off in the middle of the week?
I worked for well over a decade in a US +100y.o. global research company, who famously kept everyone working during the depression. Famously, 8 hour work days with summer work hours reduced to roughly 7.x hours because the founder respected workers and family life. Half hour for lunch, variable depending on responsibilities, excellent on-site food, a barber shop, other amenities. Significant Christmas bonus, mostly shut down over holidays, pension later 401ks. I would arrive at home at 4pm after full day in the summer and a half hour commute - and still had until after 9:30pm to garden, home projects, before the sun set. Bottom line, things got done but Wall Street doesn't take kindly to that kind of giveaway nor freedom to employees and forced a buyout. Of course I understand noone cares what I think, but I had the greatest personal and professional recognized successes and triumphs in that very environment, freedom coupled with discipline, and I simply cannot understand people's point of view when they talk of longer hours.
You can't have more money, AND fewer hours/more vacation.
If the company still paid good money, then it just means that they were a really profitable enterprise.
It's like if a company like Google which currently pays top dollar, decides to pay average market salary, but loads the compensation offer with perks and time off, then I bet people would be saying that Google is a profitable company because it gives employees all these perks, whereas Google gives all these benefits because it's a hugely profitable company.
Some people would rather get paid more (especially if they are young) then work comfortably, maybe it's too hard for you to believe but America is full of people like that.
> You can't have more money, AND fewer hours/more vacation.
This assumes that productivity is constant per hour worked, which is far from the truth for many professions. For most professions you the productivity delta not only decreases with too many hours, it even eventually becomes negative. There's no reason to suspect that eight is the optimal number of hours for every profession; it's just a historical quirk left over from the days of predominantly manual factory labor.
> This assumes that productivity is constant per hour worked, which is far from the truth for many professions.
It isn't, but productivity also isn't an inverse function of number of hours worked.
At best, productivity is a function of the incentives which drives you, to a limit, after which it comes down for the number of hours worked.
Take for example there are many people who had high paying corporate job, but once they quit it and started working on their own startup, despite the long hours they worked, their productivity went up.
Similarly, other people work for money, because that's what drives them.
The main point is that there is no one size fits all solution. But nearly all these studies about workplace hours studies fail to see that.
>This assumes that productivity is constant per hour worked, which is far from the truth for many professions.
Even in white collar that's not true. For creative problem solving it mostly holds but it doesn't hold very well in situations where the immediate product that isn't cutting edge and/or isn't mostly aesthetic (basically the artsy people and the R&D people). For everything else there's a pretty direct relationship between time and productivity.
It's true for most (if not all) white collar professions, not just the creative/artistic ones. You can't stare at Excel spreadsheets for ten hours straight and be as productive in the tenth hour as you were in the first. Or say that you're doing case research -- you're certainly more bored and easily driven to distraction after you've already been reading for many hours in a day.
It's not a quirk. There were studies done during WW2 that aimed to maximize production. They found that increasing work beyond 8 hours increased productivity for a few weeks, then it fell off below what was produced in 8 hours.
They found production was maximized with an 8 hour day, interspersed with occasional longer days.
would I be more productive with 6 hour days? probably. would I get more done? absolutely not (at least for me).
6 hour days would be a huge boon to my personal life, but I couldn't afford to be paid 25% less. even if I was 10% more productive (probably generous), i still couldnt afford to be paid 17.5% less
So, I ask you kindly, where is the tradeoff? 7 hours/day? And what if most decided that that was the norm, and maybe and as competitive forces corrected your wage would rise to match current (or oppositely prices fall to meet less free income)?
People in the software industry find it hard to comprehend the fact that many old-school companies actually don't require all their employees working at 150% thrust to remain super-profitable. Slow product life-cycles, manufacturing prowess, regulated markets, etc. mean that in many companies, you can have a fruitful career and not burn yourself out with 80 hour weeks. This is usually more true with non-software/non-service companies where white-collar labor isn't the most critical asset. In the same companies, employees in manufacturing, sales, etc. have it significantly harder than developers, R&D, etc.
One possible downside is that not everything you work on makes it to the market and you have to be proactive in keeping your skills and knowledge up-to-date and to remain employable for your next job.
> You can't have more money, AND fewer hours/more vacation.
Here's the thing, though. We don't even get a choice. I tried for YEARS to engineer a long-term part-time career in the software industry, and I couldn't get it to happen. I'm perfectly happy to trade more free time for less money, but there are just no takers out there. The industry isn't interested.
The common sentiment in articles like these is to try to appease to the owner; "look, the productivity!". We seem so subjugated by this state of affairs that worker happiness and health is not allowed to be an end in itself.
Make sure to separate the eagerness to fight and the support for less working hours. A subjugated workforce with a weak or non-existing labor movement will not fight much. However I'm sure that an overwhelming majority of workers would answer yes to "Would you like to work less hours with the same pay?".
Furthermore, there's basically no historical basis for increased workers rights/benefits coming from business owners.
I don't think most workers have the liberty to fight for their interests due to the double threat of being fired and not having a safety net to fall back on.
It's typically not an accepted proposition to offer to work 4 days for proportionally less pay (even if one does the math to fix the ratio for benefits). So it's not really a sliding scale for less time for less money, the choice is predominantly full time for more money or full time for less money. So this idea that people always choose more time and more money is a red herring.
How often do you get to actually use that flex time, though? I think most of us have plenty of horror stories about being offered "time in lieu" for overtime, and then the boss conveniently "forgets" that he offered us this.
I'd second this. All the responses to the contrary seem to be about >40 increase, but there aren't many chance to take a 20% (30%, realistically) pay-cut and work 4 day weeks.
Partly I think that's an efficiency thing - if you're critical path on a task, having you available when everyone else is becomes worth a large multiple of your salary. Partly I suspect it's just about not opening the floodgates, where people either resent you or take the same deal.
I wonder what the real cut would be, though? For work like software where adding shifts can't be done cleanly, you risk all kinds of major benefit, payroll-tax, and hardware/facilities costs. Still, there have to be programmers willing to take a 50% pay cut for a 33% hour cut.
(There's an essay somewhere for programmers about how to ask a manager for this, which is full of notes on how they'll be confused and try to reject it without considering it.)
You can certainly choose to work for a 40h company instead of a 60h company but the latter type of company doesn't seem to have any problems recruiting.
That's on the other side of the issue. My point was that there isn't anything like a 'proportional electiveness function' for the hours of work people are able to get with employment agreements. I think it looks like this for salaried professional employment: anything less than 40 is very low probability, 40-45 is very typical, and decreasing popularity in bins afterwards 50-60, 60+ etc.
Given that's the distribution, you can't say people won't don't want to elect for <40 for less pay, it's not a really a choice in the current environment.
Most tech workers could easily work fewer hours by simply leaving the office when their time is done.
Look around you and count how many people are working overtime on their own, sacrificing their life for free food, a fuzzball table, the expectations of 0.1% equity down the road, the hope of giving a good impression to their manager, the expectations of a raise later for hard work, or the pressure to work night and week-end unpaid on-call.
When not thinking about it, people choose neither money not free time :D
If someone is eating and playing fuzzball then I'm not sure I would count that as working overtime. In tech companies in particular at work does not necessarily equate to working.
I'm always confused by the hatred for people staying late at tech companies doing not-work. It's described like some elaborate anti-worker scam, but a lot of people I know are genuinely friends with coworkers (and often pretty introverted outside of that) and just enjoy doing that after work.
I suppose I can understand the conspiracy theory of "they want you to only have work friends", but I really don't understand "they're replacing a good raise with a $100 ping-pong table". It's just not a sane model of what's happening, keeping employees in the building is not inherently profitable.
It's not hatred. It's about running a business efficiently, while the employees don't even realize it.
1) Keeping tech employees in the building is profitable.
2) In tech companies in particular, you don't have to be at work behind a computer to be productive.
Once you both understand that these things are true and correct, you can begin to understand the business of the SV and why these perks come to be.
While people are in the office, they are with co-worker, thinking about work, talking about work, progressing on their work. And the magic thing is you don't have to pay them for it, because they ain't working officially.
A bad thing happen in production late? Fine, they're already there and they won't even think that fixing it is doing actual work because they are already there. That foosball table was way cheaper than paying overtime.
How about serving breakfast at 9 am and dinner at 19? Then people who wants both will stay. Most likely, people who are a bit close to one or the other might extend their schedule slightly just to grab it. But no way they think of it as extra work.
Honestly, it's people with lives external to work (families, hobbies, friends, kids) seeing people with nothing better to do than hang out in the office all day seizing the inside lane wrt office politics by doing stuff that's not related to their actual work at all. I don't know necessarily whether that's unfair, as a manager might see somebody with nothing better to do with their time but work as an asset, but I can empathize with the resentment.
I actually negotiated the possibility to take one day off per week at my own discretion, thus working flexibly between 80%-100% in ~5% steps. In my mind this is a compromise with my dream of early retirement "Mr Money Mustache"-style.
Early retirement is just something I don't see happening for a salaried worker in Sweden. Comparatively low salaries (for developers), high real estate prices and high taxes makes that pretty impossible. But now I have the choice of either taking a day off or pay 61% of my salary for that day to the government.
I spent three years making the other choice and working remotely from various beaches.
I had to stop because of how lonely and isolating it was and how I couldn't maintain any relationships with my girlfriends and the 99% of my peers that were back home working 60h a week.
>Most tech workers could easily work fewer hours for less money in second-year cities or take months-long sabbaticals but choose to do the opposite.
What universe do you live in? In my universe, this is simply not true. No tech company is going to allow you to work, say, 30 hours a week for 75% of your salary, plus full health benefits. And taking a months-long sabbatical means you don't keep your job, and you have a hard time getting a new one because of a resume gap, which employers absolutely hate.
You obviously have to be in a field like software engineering where there's a shortage of employees and employers can't get too picky about things like that.
I did it myself for years modulo the health insurance part (we have universal healthcare in my country).
I just negotiated the option to work 80%-100% (in ~5% intervals) at my own discretion. Basically I'm allowed to take up to one day/week off. I'm a software engineer working in tech.
Workers aren't eager to fight for their rights at all right now, most unions in Sweden struggle just to maintain membership numbers.
That is the most exceptional thing about the trial: that it happened at all in a climate where collective bargaining is declining and the decline of the concept of a stable job.
When I talk to Swedes they seem to be way ahead of the curve on the idea that total employment is unsustainable. I wonder if maybe they'll approach this problem from a different angle?
I've been doing sub-20 hour work weeks for a while now. I'd like to never go back to anywhere near 40.
To the workaholics out there I say stop working extra for free. Those additional hours are unsolicited gifts to an employer who would fire you if it was possible. Stop giving your labor away, seriously.
I keep meaning to write up my experiences with chronic fatigue. I spent a couple of years as a developer working 25-hour weeks because I couldn't manage any more. It's interesting to consider that while few people would ever be hired on such an arrangement, smart employers realise that it can be better to retain part of a person on partial wages than lose them altogether.
And obviously people should realise that the lack of hour restriction on salaried work can be used against them. Stick, on average, to your contracted hours; crunch time may occasionally be necessary but it should be compensated and never normalised.
Off topic, but: It sounds like you recovered from the chronic fatigue. Did anything in particular cause (or even help with) the recovery? Or did it just go away with time? Or do you still wrestle with it?
I've been doing about half your work week for years - and my salary very much reflects it - but I feel it's time to go to at least a 30h work week. Mind you, I think it's okay to be out of step with the way most of the world works. Too far out, however, and one becomes way too used to being solitary, especially in a remote, work-from-home scenario.
I have found 4-day weeks (32 hours) ideal. The workweek is over before you know it, and the weekend is long enough that you want to go back to work on Monday.
I'm particularly upvoting the second half of your sentence as it resonates personally — but moreso that I entertain a hope that such a mentality underscores the benefit and potential of Universal Basic Income, if and where economically plausible.
I'm not sure I understand your first paragraph coupled with the second one.
Do you get paid to work 40 hours, but only work 20? Or do you get paid for only 20 hours of work?
If it's latter, then the problem is that not many salaried jobs can offer such an arrangement without major caveats.
Even if you have a formal agreement with your employer for 20 hours of work, the deadlines and expectations from customers and "business" in general will not care if you are only signed up for 20 hours, when the project needs to be delivered by Monday.
It's full-time pay and yes you need to know how to pace things and schedule.
Getting better at estimates go a long way. The "20 minute" task at the end of the work day that ends up taking 2 hours ... either stop doing that or start being honest that 20 minutes meant 2 hours.
Also know what "corporate time" means. Usually the monday deadlines are dependent on a bunch of other things that are rarely if ever done on that monday. Almost universally things are days if not weeks later than scheduled. Have something to go for the monday, but anticipate the reality based on the client relations ...
Also position yourself from a business perspective. The company is doing X to make a profit. You are there to help fix a problem in achieving X. Orient all your goals only to that - not in fixing any adjacent problems - your customers ultimately don't care, your boss ultimately doesn't care, and if you did that, you just worked for free.
Can you give some more details on how you do it? Do you go to work 5 days and leave office after 4 hours, or do you just work 3 days a week? Are you subjected to daily scrum status reports requirements? Etc.
yes to all those. Sometimes I'm there 3 days, sometimes its 2 ... sometimes I'm doing an 8 hour day but only 2 that week, sometimes I'm writing and responding to emails. Sometimes I wake up for scrums then go back to bed for a few hours...
There's something called the pace of business. I'm sure there's been slow times when business is moving fine and not much is changing.
Instead of finding work, say to the boss, "I'm not going to waste your money in something that doesn't need to be done. everything is fine, here's the semi vacation I'm doing." It may come at a pay cut, but it should work in your favor and improve your trust and relationship with your superiors because you're taking responsibility for not just the work but the amount of it.
From a business owner you're essentially saying "I achieved the tasks, things are stable. Now pay me less and I'll go do other things" Sounds like a better deal then "now I shall fill up the time with tasks I claim are important that you don't understand but must pay for." From a non tech perspective, this makes you sound like a bozo who doesn't understand business.
Knowing how to negotiate and manage your own labor, especially with respect to business risk and your added value, and if you're expensive is important. Really, it's one of the primary ways you get to be expensive in the first place.
> From a business owner you're essentially saying "I achieved the tasks, things are stable. Now pay me less and I'll go do other things" Sounds like a better deal then "now I shall fill up the time with tasks I claim are important that you don't understand but must pay for."
I'm still confused. Are you formally getting paid less than a comparable full-time (40 hours) worker, or are you getting paid with the assumption that you work 40 hours a week? You said you get "full-time pay" earlier, but now it seems you're saying you actually have a special reduced pay arrangement of sorts.
I'm throwing together 8 years of doing this at 5 places. Some have been retainers, some have been contracts, some have been 2 or 3 different things. Currently it's officially full time pay at 3 days a week with each day being 6 hours. In practice it's more like 15 hours instead of 18.
Don't end negotiations during the interview. Open it up again when things change.
Engineers aren't great at business and often hand wave it off as if it's unpleasant and impure. That's nonsense. If you're an employee, the business comes first.
Get to a level of skill and track record where it's easy to find companies willing to hire you. Then, when negotiating, give up significant salary to reduce your time commitment. It works better with smaller companies (Google, etc are not going to go for this)
Join Google - it allows part time work (50%/60%/70%/80%/90%) and people do use it creatively to maximize their convenience. At or above 50%, you also get health insurance. Perks stay the same.
The way to get these out-of-the-norm gigs is to get good—so good they can't ignore you (to quote Cal Newport) or in this case that they'll say no because they need your skills.
If you get good and are known to be good, you can ask for any kind of work arrangement.
People are cornered by high rent/land prices. They understand this and hate it. The whole point behind high land prices is to prevent most people achieving financial independence. At this point the workers call the shots. This is why we are kept wage slaves.
The market structure for land and its methods of entitlement are certainly wonky and need reform ... but I'm pretty sure we're "wage slaves" because the labor movement was successfully killed off in the 50s red scare along with the rise of classical liberalism in the 60s which poo-poos collective action, devalues communal capital, and encourages uncoordinated individual action.
So when the productivity gains that were promised in the 50s came in the 80s there was no labor movement to force a shorter work week, so instead there were layoffs and bigger profits on top.
We never got the promised 20 hour work week of the 50s because collectively we forgot and abandoned the multi-generational labor struggle which got us the 40 hour one. These things aren't going to just get handed out.
We never got the 20 hour work week partially because people actually want to reap the benefits of that increased productivity, like smartphones, better food, etc. It's much cheaper to live at a 1950s standard of life.
We are also forced to spend more in many cases; taxes are higher, EPA vehicle regs are stricter, etc. I am effectively forced to give away ~40% of my work time to federal and state governments (not including taxes on the employer side, like payroll taxes), and I don't make much as a student.
Yes, land prices dominate. And who owns all that land? Not the goverbankment, but the people who are willing to work 2x50 hours per week to get the house with the 100 acre garden.
Land is a competitive good, land near commercial hubs is scarce and eventually goes to the highest earners in relative terms. If you want to cut working hours for everyone, the government has to mandate it - otherwise people will always be willing to work a smidgen more than you for the better house. The government here is part of the solution, not the problem. (Unless you are talking about municipal zoning and NIMBYism which is certainly part of the problem.)
I don't agree with this vision of people as slavish consumers. I think given the choice people would not work extra hours. If they did they could purchase a house. They would gain no advantage from buying multiple if we taxed land.
If people add more value I have no problem with them having a bigger house / more stuff.
I have a problem with being forced to work for my landlord.
I seriously have issue with calling us wage slaves and such, let alone claiming its because of the failed labor movement.
we are slaves to our uncontrolled passions that marketers have ruthlessly and easily exploited having us believe we need something we cannot afford. we allow ourselves to be convinced that our life would not be as fulfilling without the latest fad/gadget/etc.
If people paid in cash for what they want, put off such purchases for three or more days, and bought a home one income could support, there would less "slave to wages" than people think
> If people [...] bought a home one income could support
I think GGP's point was that those are becoming hard-to-impossible to find in many places, especially places with decent-paying jobs.
I don't agree with him that this was a deliberate conspiracy by employers to keep workers oppressed; I think it has far more to do with an out-of-control financial sector and governments addicted to over-loose monetary policy. But blaming people's "uncontrolled passions" for wanting a stable home, one they might actually be able to pay off one day, is a bit silly.
(Disclaimer: this is a view from London, which while it might not be quite the absolute worst for housing is pretty damn close to it. YMMV.)
Businesses extracting profit from the labor of its workforce isn't a conspiracy. It's fully disclosed to children in school and I don't think anyone challenges it.
Now if the question is whether they try to maximize profits, once again, this is not a secret or a back room conspiracy, this is how it works.
As an employee, enter into every negotiation knowing this.
> Businesses extracting profit from the labor of its workforce isn't a conspiracy.
I'm not sure you who you're arguing with. What I said was
> I don't agree with him that this was a deliberate conspiracy
and branchless' GGP comment I was disagreeing with wasn't about "extracting profit from the labor of its workforce" in general, it was about "The whole point behind high land prices is to prevent most people achieving financial independence."
This is exactly wrong. We bid for land in the main as most jobs require living in an area where demand exceeds supply (especially as demand is inflated by our land speculation system).
If we get more productive and wages rise we have more disposable income so rents / renting money from the bank (mortgage) rises.
If we cut back on consumption we have more disposable income so rent rises.
Unions for sure are part of the picture, but I'd rather take a further step back from this and give people the right to refuse to work. I'm not talking about the right to sit around all day of your life, but the right to say "you are working me too hard, I'm out for a bit".
But people cannot do this because we live in a world of very efficient economic rent extraction through land prices. When productivity rises land prices rise, handing over all gains to the banks. Our generation are, thanks to tech, far more efficient than the 1960s. Yet now both parents must work for the same (or worse) house.
Computing power brought us many things, it also brought banks, the ability to track vast amounts of electronic debt. At a time when we came off the gold standard allowing unconstrained fiat issuance.
I'd like to see the shoe on the other foot - employees who are not under constant financial pressure due to high rents demanding that employers pass on most of their surplus value.
edit: cannot reply to your comment as faux hacker news "you're submitting to fast about usury"
here it is:
The main cost of "housing" in urban areas is the land. Construction has improved massively since 1960s as has materials construction, yet here we are with housing at record of income multiples.
>Yet now both parents must work for the same (or worse) house.
That isn't true. Houses built in the 1960s that have only had basic maintenance done to them are available and they are a lot cheaper than newer houses. It turns out most people don't want to live with a house that looks like the 1960s. People like bigger kitchens and houses when we can afford them. Once the house gets a little bigger we like to see things like brick on the front (I'm not sure if this is styles changing or a longer term pattern of people deciding the houses of 1990 are big enough and now we want pretty not more space).
The result is perfectly nice houses in old neighborhoods are available for cheap if you are willing to live in them.
Despite the above I recommend you not buy those old houses: they are not energy efficient and so either heating/cooling will eat your paycheck or you will spend a lot fo money in upgrades you won't get back.
Welcome to the Bay Area where tiny 50+ year old homes in decent (read: not crime ridden) neighborhoods with only so-so schools go for $1.2+. And those are often ones needing a lot of work.
The trade off is a very healthy job market, phenomenal weather, a great liberal culture and great food.
The 1960s were pretty close to the nadir in quality for residential construction in North America. Most of the old growth forests were already gone by that point, and builders had yet to learn how to build durable structures with younger and engineered woods. Combined with primitive insulation, nonexistent air-sealing, and an extreme carpeting fetish, this lead so some of the worst residential structures ever built.
>It turns out most people don't want to live with a house that looks like the 1960s.
I do.
>Despite the above I recommend you not buy those old houses: they are not energy efficient and so either heating/cooling will eat your paycheck or you will spend a lot fo money in upgrades you won't get back.
Ah, and there's the problem: not freezing in the winter.
In the US farm land averages under 4,500$ per acre. Now there are not a lot of physical jobs in those places, but if you are willing to work remote that's a non issue. On the other hand the median house in Iowa costs $126,300 a but a of cheap housing is less than that and just rented or constructed by the final home owner.
In large part people live in city's because they want to live in cities. I pay close to 1/3 of my take home pay in rent because I like where I live.
Most 'office' jobs can be worked remotely. A lot of jobs that do require face to face interaction also involve a lot of travel and can therefore be based anywhere near an airport.
Right now 20-25% of the US workforce teleworkers some of the time. And up to 50% of US jobs could be worked remotely a significant portion of the time. Further, as people move out of the most in demand city's service jobs will follow.
> Most 'office' jobs _CAN_ be worked remotely. A lot of jobs that do require face to face interaction also involve a lot of travel and _CAN_ therefore be based anywhere near an airport.
Right now 20-25% of the US workforce teleworkers some of the time. And up to 50% of US jobs _COULD_ be worked remotely a significant portion of the time. Further, as people move out of the most in demand city's service jobs will follow.
Quoted with emphasis placed. Can, could, sure I agree 100%. The ability to do this lies with the consent of the employer, not the employee. A lot of people don't have the luxury of cherry-picking their income source, and are beholden to the rules of their employer. I realize that notion isn't really considered here: "we can all get jobs anywhere, we're smart devs!", but in reality is isn't true for large swaths of people.
Personally, I did it for six months, but I don't actually want to work from home. I live within five miles of my office and enjoy a clear work vs home seperation. So, I don't think this is really limited to what companies want.
That said, my office has flexible hours and a liberal WFH policy which is a huge deal to me.
This isn't quite right. Most 'office' jobs could be performed remotely is true. You can't say they can be worked remotely because most companies don't want to deal with remote workers.
Having a 1.5-2h commute 5 days a week is soul crushing, having a 1.5-2h commute 2 days a week is not. There is cheap housing within 2h of most locations.
My boss lived 230 miles from the office at my last job. He showed up 1-2 days a week for meetings and that's it.
What would you suggest to the vast majority of people who are not developers and likely could not become one? It is great that your situation allows it...most people's do not.
Testers and cold callers are far less in demand than developers and they still WFH fairly regularly. It's not a 'privilege' so much as a way to reduce costs by having to pay for fewer desks and thus lower overhead.
A huge swath of people simply don't like to do remote work for very long which has a lot more to do with current trends than you might think. Anyway, while there are basic requirements as it's hard to do construction remotely for example there are far more opportunity's than you might think for people with even just a high school diploma, they just don't necessarily pay as well.
Welcome to the real world - not everyone's skill set commands the same benefits. You don't see a lot of people asking LeBron James how to make $40m/yr without any talent and physical ability, do you?
If your 'situation' doesn't allow the benefits/compensation that you want, you can either change your situation or change your expectations.
So... if your house appreciates it's because you are attempting to prevent others from achieving financial independence? If you earn $50K are you attempting to prevent workers in Mexico from earning $50K?
People are cowed by their employers, with little to no savings they live month to month and dare not say no to extra work tasks such as email in the evening etc. High rents are squeezing all disposable income leaving people with no financial autonomy.
For me the american dream was all about financial autonomy. The USA had to have actual slaves because they had no land enclosure. Why work as a wage slave when you can walk up the road and work empty land? Land gives labour the choice. Land enclosure is required for wage slaves.
> During the first 18 months of the trial the nurses working shorter hours logged less sick leave, reported better perceived health and boosted their productivity by organising 85% more activities for their patients, from nature walks to sing-a-longs.
How do you eliminate bias in a trial like this? I mean, a lot of people want to move to a 6-hour day, so they'll be working hard to prove they're productive in that format. That doesn't mean it'll be sustainable though once it becomes the new normal.
I'm very much in favour of shorter working days, but here is one way you can "pretend" to be less sick:
Being sick is not a binary. We've all had days wher we feel like shit but figure we don't feel quite ill enough to stay at home, and so end up taking a couple of painkillers and favourite source of caffeine and end up working.
Presumably the shorter the work day, the more likely you would be to consider it ok to push through it if you feel ill, especially if you have vested interest in demonstrating that a new arrangement like a 6 hour day "works".
I'm not saying they did, but there are many ways they could plausibly sustain something like that for quite a while. The question is whether it is sustainable on a long term basis, or if it would change if/when a 6 hour day is no longer an experiment.
It doesn't if the effect persists. Hence the last line of my previous comment: It does matter if people eventually goes back to the old behaviour once they feel "secure" about the 6 hour day.
To be clear: I'm not stating a belief in terms of whether or not people do this or not, but it is a tricky confounding factor to exclude, because everyone involved in an experiment like that will have vested interests in the outcome that might significantly affect how they act.
It's not like you can double-blind a study like this. Ultimately it will likely take long-term studies from places that actually implement it on an ongoing basis over much longer time frames to get a true picture of the effects.
That said, as I said, I'm all for working fewer hours. I just don't think figuring out what the cost/benefit tradeoff is will be remotely this simple.
Agreed. Not fully sure why we couldn't move there in steps. If 6 hours helps a lot, 7.5 hours should also show some improvement. And the cost to the economy is much smaller in case it's not working out.
Maybe I am not thinking about this right, but if I feel like I can more effectively plan alternative activities that fit into 2 hours than I can an additional activity that would fit into 30 minutes. What I am saying, is there is no reason to believe that the benefits are linear.
Think of it in another way, if I have to work one hour from 12 to 1, it removes any alternative activity that requires the whole day. I am just saying, that assuming it is a linear benefit is too big a jump for me.
I thought so, too, but found in reality it's actually helpful. On one hand it doesn't really matter if you feel you have more time. On the other it also drastically increases your flexibility if you need to take off a few hours once, since that doesn't put you behind as many hours.
I'm actually a Swedish business owner (me and co-owner) doing 30 hour weeks. One of our main goals of starting our digital consultancy was to work less but receive same or better pay. It works well for us. We're at least as productive as we were as employees.
The main difference being we cut out "fika" - this was easily 60 minutes per day at our old work place - and dropped all private web lurking from the work days. We just decided we didn't need all that downtime from doing work during days, we'd rather spend it at home.
Clients are pleased with the work, I get to both drop and pickup up my kids everyday. In Sweden, if you've got web dev skills, this is very doable.
I believe in it on a bigger scale for worker happiness sake and really hope we'll get there soon.
From the first google result: "Fika is a common practice at workplaces in Sweden and Finland where it constitutes at least one break during a normal workday. Often, two fikor are taken in a day at around 9:00 in the morning and 3:00 in the afternoon. The work fika is an important social event where employees can gather and socialize to discuss private and professional matters. It is not uncommon for management to join employees and to some extent it can even be considered impolite not to join one's colleagues at fika. The practice is not limited to any specific sector of the labor market and is considered normal practice even in government administration."
This is a good interpretation of the term. Sorry for not explaining the concept of fika :)
My company is a bit weird in the Swedish work culture since we don't really go for breaks at 9.00 am and 3 pm. But we get to go home at 3-4 pm because of it.
I realize that this is privileged and that the fika fills an important need for a break during more physical or mentally demanding work.
"I thought it would be really fun, but it felt kind of stressful," says Gabriel Peres, as he slots a Petri dish inside one of the 3D printers he's built for the company.
"It's a process and it takes time and when you don't have all that [much] time it kind of feels like skipping homework at school, things are always building up."
That's a perspective I hadn't considered. Maybe the 6 hour work day makes more sense for service-based work like nursing, fast food, etc.
For us techies it could actually be a nuisance (depending on how the individual works).
For me, some days it would be awesome, on others it would be stressful as shit.
What I would prefer is to work as long as I need to and when I come to a logical breaking point, I go home. Some days that may be 4 hours, other days that may be 12. Some things I can't easily break down into chunks that easily fit into 8 hours and not have me lose my place by going to sleep. Some days I get into a flow and I don't even realize I'm hungry until it's dark again and I suddenly realize everyone's gone to bed and left me on my own. Other days I struggle to figure out what I'm doing and the more I fight it, the harder the struggle becomes. It's not because of a lack of discipline or lack of want to work, it's just that I struggle to connect dots that when I'm on form just connect themselves.
On days when I'm on form, I'm unstoppable, a machine that just churns out working, tested, simple, elegant solutions to problems. When I'm not on form, I can't figure out how chew gum without gagging. This seems to hinge on how much sleep I've had, which directly impedes the amount of time I have in a day... finding the balance between enough sleep and enough time to get work done to a high degree of quality is a constant struggle
So I don't think changing the length of the work day for me even enters in to my psyche. It's always either far too long or nowhere near long enough... it would be the same if the work day was 2 hours long or 22 hours long.
That's what it's like for me, I can't speak for everyone else.
That's what I did as freelancer. I often did my 40 hours work week in 3 days. And I think I did better work that way. In my corporate job I often don't have an inspiration at 9 am so I pretty much sit around and pretend to be busy. It would be much better to take off that time. And then you have that moment where everything makes sense and can crank it out in 18 hours.
Unfortunately programming is treated like assembly line work where every hour (and every worker) is equal. I don't think this reflects reality well.
I used to do this early in my career too, until I realized how counterproductive it was. I've found that it isn't "coding marathons" themselves that are good, but being motivated, undisturbed, structured etc. Few people are that everyday, so we have to work on it.
Nowadays instead of coding full out until I go home and crash on the couch I try to spend the last hour of the work day documenting what I've done, what need to be done tomorrow and even what I'm doing this evening. That way I've probably had some decent time off, I know what to do the next day and can more easily get started. Even if I'm not motivated I can do something simple for a couple of hours, at which point I usually get motivated again.
Coding marathons feels good when you do them, but they also builds up debt. Both in the structure of the project and in motivation. It's quite natural that it's hard to get started if you don't have an obvious starting point and you anticipate that you have to do a full 8 to 10 hours and be completely spent at the end.
Yes, it's not the coding marathons themselves, it's being in a moment of intense focus and flow where your fingers really seem to be coding on their own. Time becomes meaningless, ceases to exist even because you're lost in your own world and everything just makes perfect sense.
What I'm saying though is that we perceive "coding marathons" as good because we can only do them when we are in a good state. Say you have five coding sessions and in four of them you run into some problem, you get disturbed (or demotivated) or something else that halts your progress. While in the fifth none of that happens, so you end up having a long period of "flow". Then one might conclude that it's the coding marathon or the flow itself that is good when in reality it's the really the other factors that correlate with having a long session that really matters. And if you practice you can make more headway each day, even achieving flow in shorter sessions, than you ever could only being motivated to do coding marathons sometimes.
I think what you are trying to say is consistency is better than inconsistency given the same amount of work. The consistent worker will be able to get items done in 5 days, but the inconsistent one will take 3 of those days, do the work, then twiddle thumbs at work for the next two days to regroup. Both are "ready" back on the start of day 1, but which one is more efficient?
One could argue that the person can make a better use of the two extra days spent working but not productive on items related to specific work items. So it may not increase productivity to the employer but it increases productivity to the employee.
of course, there are moments of interrupted zen as you describe. But I was mostly not considering interruptions, distractions and diversions. I was mostly considering that if I were left to my own devices entirely undisturbed... you can have a half hour, hour, 2 hour or however long you're in your state of zen coding marathons... perhaps I don't consider them coding marathons as such, perhaps I consider them more like a state of meditation. Though, I could see how other people would describe them as marathons.
Alas, there's only one me, so your company probably isn't :P
I kid around. Of course, we're all human and we're never all on form on the same day and shit happens and unexpected problems need to be solved right now and the only guy on form has no idea of the problem domain and the only guy who does understand it is 20 hours into a 22 hour day and has bloodshot eyes. This is life, reality. Sadly it doesn't understand ideal. It's all about compromise for the greatest good we can achieve today to meet our goals tomorrow.
This rings quite true with my experience. There are days where I leave early because I'm not being productive due to…you know, just the brain being weird.
> What I would prefer is to work as long as I need to and when I come to a logical breaking point, I go home.
The only issue with this approach is that what you perceive a logical breaking point and what your boss perceives as a logical breaking point will be very different. "Before you go, can you just fix ..."
Even 8 hour days can result in this behaviour becoming 10+ hour days.
That's true... I think we need to be more congizant of this - if I fix this one thing now, is it going to significantly improve ROI over if I do it tomorrow when I'm well rested?
I know someone who asked to go from salaried to hourly for this reason - he didn't want to sit there and ride the clock if he wasn't actually able to be productive during that time.
The (engineering) company operated based on billable hours, so they loved it, initially. Eventually, though, you stop fitting in to the organization when you're a part-timer.
It doesn't really make much sense to talk about the length of a work day except on average. "Six-hour work day" should just be interpreted to mean "120 hour work month" or similar.
I think many of us on this site have jobs where presence and productivity are pretty elastic.
Many workers have jobs where human presence is a key part of the job function. Being a cashier, or a nurse, or driving -- it isn't as though these things happen unless you are physically there. The quantum of human presence is "one human" :-) so even if there are no customers, the driving is boring, or the patients are asleep, it still requires you to be there on the job.
I suppose it depends whether six hours is a hard maximum.
If you're being kicked out of the building in six hours, that could be stressful.
But if six hours from now you have the option of leaving with no one looking askance, that's nice. (Until everyone tries to prove they're more hard-core than the next guy.)
It seems like the tech sector _was_ starting to realize that people can get more done in five hours of "flow" than eight hours of forced confinement to a desk.
> For us techies it could actually be a nuisance (depending on how the individual works).
I doubt very many people can regularly engage in 6+ hours of deep work, day after day after day. I think a more common pattern is 3-4 hours of deep work, then a similar amount of time processing email, playing code janitor, going to meetings, and screwing around on the web.
For some jobs, that might be the case. Other jobs... well, it doesn't matter if you work for 6 or 8 hours, you work just as hard. You don't get email breaks, just a couple 10-15 minute breaks (if you are lucky) plus a lunch, which can be as little as 30 minutes. Those two extra hours make a huge difference in energy levels. Cashier, nurse, CNA, janitorial work,factory workers and likely construction crews to a point. Teachers, in a way, have this as well, only theirs is counted in number of classes they teach and the amount of kids in the classroom. Teaching 6 periods of class is different from 7, for example.
I'm "salaried", technically hourly but guaranteed 40-hours/week. They haven't approved us for overtime or comp time so I'm done when I hit 8. That hard stop has motivated a great deal of my automation at work. Projects I got pulled into had me doing 2-3 hours of busy work a couple times a week. Things that occupied my PC and attention for way too long. A handful of scripts later, I cd to the right directory, type the right command, and get back to whatever I'm supposed to actually be working on and that work that used to take almost a full day a week is done in the background in 20-30 minutes (less once they replace my computer with a new one, hopefully soon).
Perhaps tech workers could instead work three ten-hour days instead, if indeed it's not just a symptom of deeply ingrained conditioning towards work-a-holic behavior.
I have a hard time accepting "please just let us work longer again" as the only viable option, or even close to the most popular one among a group of employees.
* if you have a job that requires X work be done. The more productive, happier employees still get X work done. If I'm happier and suddenly don't spend 2-3 hours of work time on reddit or hn, I can actually get MORE work done in less time. I imagine a lot of HN style jobs fit into this category. I know I can write more code when I'm well rested and thinking clearly.
* if you have a job that requires Y hours be worked. You have to hire more staff to cover the extra hours. For example, hospital care (like the lady described in the article). If you need a hospital staffed 24/7, you now need 4 people to staff a single day instead of 3.
> if you have a job that requires Y hours be worked. You have to hire more staff to cover the extra hours. For example, hospital care (like the lady described in the article). If you need a hospital staffed 24/7, you now need 4 people to staff a single day instead of 3.
That's the equation in its simplest first-order form. There are lots of factors you can put in the equation, of which you mentioned a few:
- reduced employer cost for recruiting if people are happier in their jobs
- reduced employer cost for sick leave/temps if employees are healthier
- increased efficiency because employees are more efficient/make fewer mistakes
- reduced healthcare costs for society if everyone is healthier
- increased employer cost of training and education if more people need to do the same task
- ... the list goes on and on.
In a society with publicly funded healthcare, the cost of sick workers is triple: first the employee is replaced by a temporary, often more expensive nurse to fill in. Second, society pays the insurance/sick leave for the person home sick. Third, the sick person now causes more work for the same public organizations (healthcare). The costs of people in working age being ill is one of Swedens largest econommic problems at the moment.
In a small scale experiment the large scale effect of a healther population can't be seen in the direct economic outcome but it can be estimated.
Well, yes, people here sometimes forget that not everyone sits behind a desk for 8 hours a day(in which case, sure, you are only productive 3-4 hours a day).
There are jobs which require 8 hours of being present, doing something or not, and by reducing that time you simply have to hire more people.
I've worked in or near operations for my entire career and if it were not for $30K/yr cost of medical insurance it would be much cheaper to hire 4 people than 3. With 4, when someone is sick or it takes months to replace someone who quit, obviously experience shows 3 can handle the load of 4 much easier than 2 can handle the load of 3.
Has anyone ever studied the effect that happens when some people are faced with data supporting a given position they argue the exact opposite? It's a sort of tone deafness, I think.
From TFA:
"So I don't think people should start with the question of whether or not to have reduced hours. First, it should be: what can we do to make the working environment better? And maybe different things can be better for different groups. It could be to do with working hours and working times, but it could be a lot of other things as well."
Well, yeah, but a comprehensive study just showed that reducing working hours gives a tremendous improvement to the quality of life and number of jobs in an area. So why shouldn't we look at it?
I am all for having nurses and doctors work 6 hour days for regular pay. The idea that doctors should pull 24-48 hour shifts in hospitals is insane. The cost of this is virtually nothing compare to other expenses in hospitals.
They say the reason is to minimize handoffs and communication snafus (double-administering meds, for instance). That's a good point, and maybe a reason to have longer shifts for now, but long-term, there should be significant investments in hospital infrastructure so unforced errors are harder to make.
People are always asking on here "what are some inefficiencies a startup needs to tackle" and I think this is a great example: Hospital support software.
From what I've heard and seen it's a total nightmare across the globe in almost every use-case. Just having a way for doctors and nurses to put all information in one clear place while also combining with the infrastructure to enforce certain information (e.g. when medication is retrieved from storage, for who is it, and was it pre-approved) to help prevent things as double-dosing (or forgetting to dose).
Doesn't sound easy tbh, but if you want a challenge here it is.
The cost of this is virtually nothing compare to other expenses in hospitals.
In the UK, the health service wage bill makes up a decent chunk of the total cost - around 39% (£45.3 billion against a total spend of £115 billion) [1].
I was tempted to post an Ask HN the other day titled "Are Americans F-ing Crazy?" after seeing how, after only an extremely busy month, my coworkers already seem shot and burnt out.
It's an architecture firm (buildings, not software) and I'm one of the few that works only 40 hrs/wk and gets to walk out on time every day and never work on the weekends. So many people came back from the holidays sick, mainly I think because their bodies were so fried from the prior year that it finally caught up. Now, they're back on that cycle.
As IT support, I get to hear it all. The father of two that told me he needs to keep a laptop checked out so he can answer questions sent at 1 am. People that were given laptops so they could work remotely, but instead just work nights and weekends. A new mother, already back into the swing of working 10-11 hr/days and maybe a little more at home when the kid's asleep. Constant work on weekends.
And that's all for salary. For free work. For what? Great for the clients and the business owners but it makes no sense to me. Seems like a product of poor planning, client management, and the powers that be never saying no.
I've done the client services work in a previous life, the 80-100 hr weeks. Luckily, I was paid for each and every one worked, sometimes making the more in double time than my base 40 week. Burn out and depression easily followed and made some hard choices (and took some pay cuts) to transition to something a little more doable and a bit more balanced.
They live that chaos because they're taught in school or inculcated in their first jobs that that's how things are. Is it because my generation (I'm early thirties) is struggle to pay off debts (school ones, in the tens of thousands for some) while also trying to do all the things our parents did? Have a house (median price in LA - $610k) or raise a family (one kid - $250k before 18)?
It just strikes me as insane sometimes that this how we set ourselves up.
Maybe it's purely anecdotal based on past near decade in a major city. I'm from a rural place and life can be a bit easier, at least if you have family and friends near.
Sorry for going off on a rant but I was so saddened when looking around a room that day (open office, of course) to see how terrible people looked and it made me think "Why can't we do better?"
Strangely, this wasn't mentioned in this or the other English-language articles about this that I saw:
The setup was to during 23 months test if six-hour days resulted in any meaningful improvement on the (rather high) amount of sick leave the employees used.
The conclusion was that the amount of sick leave only went down with 0.6%.
I commented on the previous thread about this, but I work somewhere between about 4-5 hours a day on average I think, have been doing so for the last 6 months. My productivity is now greater than it was when I worked 8, and I'm more relaxed and happier.
I'm a contractor so it's relatively simple for me to do this, I'm in a lucky position in that I can afford to not work 8 hours, but personally I can really see a huge benefit.
Out of curiosity, is this a result of your employer having flexible working hours and you being able to get the work done in that time, or are you also being paid less? (or are you in freelance, etc?)
I moved company last July from a full time job to contracting elsewhere.
I'm now a contractor in the very real sense. I use my own computer, I work generally when I want to (I set the total hours at the beginning of any month and choose what hours to work when within that framework).
In terms of pay, becoming a contractor means my pay went up and I can work 4 hours a day and do as well as I was full time, though I do try to work more like 4.5 - 5 hours a day (gotta pay that mortgage down).
What this means is that I generally only work when I'm motivated and "feeling it", the rest of the time I relax, learn, program, climb etc. It may seem like I'm expensive at > 2x what I was on when full time, but I think I'm giving way more for the time I put in, eg. no % of an 8 hour day spent being tired or "slacking". For instance I stopped the clock to read HN :) I'm also way happier than I was before.
At least for software engineering we should realize that after some time(probably 3h) per day/sleep we are doing negative work. At that point we are most likely creating more problems/bugs than working code. Actually this just reminded me of the gitlab incident and many others that happened to me and coworkers. The most damaging mistakes I can remember seem to always be linked to tired people coding.
Why didn't they scale back pay proportionally? Or would that make pay too low per person? Maybe I'm severely overpaid as a developer, but I would take a 25% pay cut for 25% less work.
That would make pay too low for e.g. nurse to be an attractive job, yes.
It's possible that if this is tried in larger scale that e.g. employees will be offered either 90% pay for 80% work, or that a deal with unions is to freeze wage increases for N years in exchange for ever shortening work hours.
> Maybe I'm severely overpaid as a developer, but I would take a 25% pay cut for 25% less work.
As a swede and parent I'm entitled to that while I have kids < 8yo. Really good set up I think.
It's comparatively low considering the long education. It's higher than in other service jobs like retail but lower than for blue collar industry work in the privatd sector.
Is this really proof. These nurses knew that they were the subject of a study, they knew that the hours were temporary, and they knew that if the outcome was positive they may get to work less and get paid the same for the rest of their lives. Of course they had a very strong incentive to organize more activities and be as good as possible for the trial period.
If you really want a study, try finding workers in a factory who work 6 hours and then compare their productivity to workers in a different factor who work 8 hours.
This seems the more obvious choice for worker happiness. Also would give more time back to both emplyee/emplyor as for the former you dont have 5 days commute and the latter for things like nursing there is less handover times and similar prep.
Also I imagine if a bloc of countries did this en masse it would limit any detriment. That said I'd prefer 10hr days, which often is the case anyway, if I could get a 4 day week!
I have a strong belief that I have no proof for that our society would be more productive if wages were such that people didn't have to worry about their next paycheck or their replaceability or their hierarchical fetters of restraint from free responsibility. Seems we get stuck in local optima by being "good responsible hard-working employees"
* i'm a software developer in central europe.
* i suffer from delayed sleep cycle (i.e. i'm a night owl).
* i picked up weightlifting (as the main hobby) to compensate for all the sitting and the club has fixed workout times in the evening (i.e. no 24/7 gym access). the harder i work out, the more sleep i need.
i used to work a 42 hour work week (from 7:30am - getting up at ~6:30am to ~6pm) at a small web dev company in the countryside for 2 years. close to the end i was practically burnt out, close to tears every evening and broke out in celebration when they told me i was fired. even after 2 years my sleep cylce hasn't normalized - i've been constantly sleep deprived.
afterwards i got another software dev job at a company in the capital where i first worked 25 hours and now work 30 hours a week with flexible time - roughly 6 hours a day monday to friday, no core time (except for scheduled meetings).
i get paid more for those 30 hours than for the 42 hours in the first job, but have less money at the end of the month because i used to live with my parents at the first company.
there are a lot of differences (more competent superiors etc), but personal observation regarding work culture and time:
* i'm usually well rested: due to flexible time i rarely set an alarm and wake up on my own depending on when i went to bed and how much i worked out (or boozed) the previous day. this means sometimes i'm in the office at 3pm. sometimes 7am. doesn't really matter as long as i don't have any meetings (which are very rare; currently once a week at 2pm). if i want to stay home for the day i send my teammates a message.
* stress level is extremely low because i can always take time off without much bureaucracy if i have to attend personal matters.
* due to only working 6 hours a day i can easily accumulate overtime which isn't paid but goes into an 1:1 overtime pool. this enables the next point:
* i rarely sit idle. if there isn't any work to do, i'll go home. period. if there's a lot of work to do (and i'm in the zone), i'll happily stay longer. it evens out and i never idly wait for the clock, passing time. i usually work more during the winter and less during the summer, when customers are on vacation.
* if i'm feeling unwell but not sick (or not sick enough for sick leave) i work from home and take frequent naps. if i'm sick it's rarely for long because coming to work sick is heavily discouraged and i just stay in bed. i go back to work as soon as i feel healthy and ready even when my doctor approved more sick leave.
* if my concentration is slipping and i don't get any work done, i call it a day. if i'm super productive and in the zone i stay because i want to.
* because of all those things i love working there. i think my employer is fair, understands efficiency and treats us employees well and i wouldn't want to cheat the company because "do as you'd be done by". i wouldn't call in sick if i had a hangover (or are otherwise unfit to work due to my own fault). if i work from home i don't do the dishes on company time. i'm honest - and so is my employer (as far as i can tell - i never caught them trying to cheat me). loyality is high; in case i suspect a colleague of cheating i'm actually on my employers side and tell them to quit their bullshit because of self interest (i don't want to lose those perks).
* i don't think i could deliver the same bang for the buck with an 8 hour work day because i wouldn't be able to accumulate the overtime i'd need to take time off if i'm not at my best. but if i wanted more - or even less - that'd be possible.
* i still earn enough to get by comfortably.
* i don't have kids yet but many of my colleages do and they love working part time because it makes things so much easier and enables them to spend more time with their offspring, even though they earn less. but this way their spouses can work more and earn more, so it evens out - and they can share responsibilities easier.
TL;DR: in my opinion 30h/week is the best bang for the buck for both me and my employer because i only work when i'm productive, so the company doesn't have to pay for my idle time and i can minimize stress and frustration. i understand this is partially possible due to the nature of software projects (deliver on time, but it doesn't matter much when you do the work).
edit: also, i can do 6 hours without the mandatory 30 minute break, if i'm in a hurry.
edit 2: i can't offload work to teammates. if i take time off, work just accumulates. no cheating!
I work an 8:30-5:30 job and this ensures that everything I need to do outside of work during normal business hours builds up to consume my weekend. I know several people who work for business with half-day Fridays and that's when they get all of their outside-of-work things done ensuring that their weekends are actually free for doing the things that they want to do.
If you have kids this is an even bigger deal. If you don't, you're free for whatever every evening. If you have kids, your after work time is committed until they get to sleep every night. Having that work-day time when your kids are in school becomes HUUUUUUUGE.
I also know people who work for CVS doing 12 hour shifts with a limit of 80 hours over the course of two weeks. This leads to a lot of full days off every 2 week period...and they love it.
It's less about the "X hour workday" and more about the "X hours of free time during regular working hours"