In my experience, the biggest obstacle is the amount of time dedicated to communication/coordination overhead like email and meetings. If you're already spending 20 hours/week on that, then you're left with only -4 hours/week for productive work. This is likely the reason why it worked well for an independent, "greenfield" project.
Ask HN: 16-hour work week jobs?
81–90 of 267 posts
Re: Ask HN: 16-hour work week jobs?
#82Earlier quoted context omitted.
Yes, I tried it several times, both working for other people, as well for my personal projects. I managed to pull out some full weeks of full-time, full-throttle work, but it is completely unsustainable. This is, social life, other activities, having out of the box solutions and ideas, friends, family are all strayed aside as secondary, weekend concerns. Work was the primary concern. That progressively led to loosing…
Sounds like adult life.
As soon as people start openly discussing the possibility of a different way of doing things, there will be subcultures that spring up around the idea. If it ends up working, the subculture can eventually spread to the mainstream. It's a very worthwhile discussion to have.
Re: Ask HN: 16-hour work week jobs?
#83I am in my early 60s and I am retired now except for a little consulting and writing a book or two a year. That said, starting in the early 1970s working at a large defense contractor, I got in the habit of only working 32 hours a week (took Mondays off). I continued this process with several other companies until about 15 years ago when I converted to having a lifestyle 1-man consulting business. The deal is however…
Re: Ask HN: 16-hour work week jobs?
#84I have been working 25 hour weeks for a little over a year now, but agonizing over finding a good number for years before that. I've found that for difficult problems to crack, I may only work 1 or 2 hours per day. But for easier stuff like initial setup, a little refactoring, translating wireframes to layouts, etc, I can easily manage 6 or 7 hours per day. 8+ is too much, and working 3 or more days in a row at that…
Re: Ask HN: 16-hour work week jobs?
#85Earlier quoted context omitted.
This is an interesting point, but it assumes that one's 'purpose' in life is to work. That's a pretty sweeping assumption, and one which the guilt is predicated on. Any idea why you feel this way? Would it not be just as valid to say that one's purpose in life might be, for example, enjoyment? Or helping others (not necessarily through a job)? In which case you should feel pretty guilty about going to work for 40 of…
I'm not sure it's bad to feel guilty about this. I'm more interested how people who don't feel guilty see life. I mean surely at some point having aimless fun starts looking a bit like wasted time in someone's life, no? We live to give our tiny contribution to humanity, and we do it by creating something through work. That also brings joy, and we do it to help each other (deviations notwithstanding). But it's a meani…
Also, consider this: instead of having two people work 20 hours a week we're having one person working 40. Shouldn't that person feel guilty about taking the opportunity to contribute and being valued from somebody else?
As for creating contribution through work - are we talking about salaried work? What about volunteer work then? If by work we mean anything that adds value whether we get paid for it or not, it's not always so obvious. The lines between enjoyable hobby and work are blurry at times and an author who writes for fun could end up creating a piece which inspires millions.
In the quest for maximizing collective productivity of the humanity we could start introducing teenagers into workforce as soon as possible and scrap the retirement age. Maybe we could even leave out one or two public holidays and add couple of work hours on Saturdays. Some would complain, sure, but overall we would become more productive.
Personally, I don't think that's the way to go. 40-hour work week is a relic of the 19th century and time is a poor indicator of productive contribution.
Re: Ask HN: 16-hour work week jobs?
#86These jobs are more common in startups and almost never found in going concerns for obvious reasons (there is no green field).
It's worth pointing out that hopping from one greenfield project to the next with low pressure isn't going to expose you to world-changing opportunities.
Re: Ask HN: 16-hour work week jobs?
#87As an enrepreneur, having to now hire developers for my startup, I don't see how this could work practically. As a company, there are objectives you need to meet by a certain time frame. If there's a task that needs to be done in 3 weeks, and there are 2 weeks of full time work estimated in order to do it, you're not going to hire someone and let it take 4-6 weeks just because they don't feel like working a full week…
> But in practice, as an employer, I don't see a practical interest from my perspective I'd venture that may be because you view programmers as interchangeable cogs. Rather, for one developer, a project may take two 16-hour weeks, and for a less talented developer, it may take three 40-hour weeks. If you need it done in 2 weeks but the price tag is the more talented developer only works 16-hour weeks, and you accept,…
The problem isn't there... The problem is finding that developer in the first place. As you mentioned, that type, is probably closer to the 10x developer profile, and most developers are cross, are (by definition) closer to the average. So the problem is, as an employer, I have to (despite both yours and my own wishes), prepare for the average case scenario, until proven otherwise that I have a 10x developer on my hands
Re: Ask HN: 16-hour work week jobs?
#88Earlier quoted context omitted.
I'm not sure it's bad to feel guilty about this. I'm more interested how people who don't feel guilty see life. I mean surely at some point having aimless fun starts looking a bit like wasted time in someone's life, no? We live to give our tiny contribution to humanity, and we do it by creating something through work. That also brings joy, and we do it to help each other (deviations notwithstanding). But it's a meani…
Isn't that a slippery slope? Even if you worked a "proper" 40-hour week you could always ask yourself why don't you devote 41 (or 42, 43, and so on) hours per week for work. One could argue that your productivity plummets as you work more hours, but in absolute terms you're still getting more work done. Also, consider this: instead of having two people work 20 hours a week we're having one person working 40. Shouldn'…
So it's about finding one's balance. If someone's balance is 16 hours a week, so be it. I just find it a bit unlikely though.
Re: Ask HN: 16-hour work week jobs?
#89I've been working independently for some time now and I've noticed exactly the same thing - productiveness is significantly better when working less. However, I do handle many projects at the same time, but for each project I only hand the time when I've thought out what I'm going to build and how. I've also found that doing so gets you straight into the coders high. It's like that once you've set your mind onto the…
Re: Ask HN: 16-hour work week jobs?
#90I negotiated a 4/5 work week with an ex-employer of mine at 80% of that previous salary. I'd say work somewhere, prove your worth, then negotiate a better arrangement.
I'm tired, but isn't 4/5 the same as 80%? How is that a better arrangement other than working less?