Poll: How many hours do you work a week?
Sometimes it feels like I work really hard. Other times not hard enough. The Hacker News population seems a relatively hard working group, so I thought it would be informative and interesting to see what the average hours worked is on HN.
65 comments
[ 3.7 ms ] story [ 135 ms ] threadOf course, if work is sufficiently interesting then I end up spending what free time I have thinking about it, which can make my work time incredibly productive, obviating the need to be "working" too much to begin with.
But most importantly: YMMV.
I suspect most people inflate the number of hours spent working (or count things like hacker news as work.)
This would seem likely to encompass the majority of HN's readership, startup crowd aside.
I'll stop soon, probably go full time consulting so I can actually have a life.
Best of luck.
Programming is awesome, especially in Perl :D
As a few people have mentioned, this number of hours is rather unsustainable, and I wind up burning out every 2 months or so for a week or two, where I put in a usual 40 hour week.
5:00am - 10:00am
10:00am - 6:00pm 13hr/day * 5 days/week = 65hrs + anything I can sneak in on weekendsI aggressively work on work/life balance and take frequent breaks (a great habit leftover from my days as a smoker), so I don't spend much time staring at the screen -- I use this time fairly efficiently.
* I'm getting back on track after my wedding and honeymoon, so I'm not yet completely back in the groove yet.
How granular do we get in defining what qualifies as a "work hour"? Do we not count bathroom breaks? The time it takes the computer to warm up? The milliseconds between keystrokes? "Work hours" will always be an issue of semantics. Here's my definition: any time I'm not dragging my feet about accomplishing a work task. Here's my tautological definition of a "work task": a task I perform for work.
Do you ever drink, go out, etc?
I'm asking because I'm a morning person, but I doubt I would enjoy 'getting to it' at 5am everyday. Although there is allure to that amount of focused 'personal time'. Doing all that after day job would not appeal to me as much.
This thread has taught me more about how different lifestyles are than anything. I think the actual hourly rate of many people in IT roles might be in a tight band (until you've 'made it'). This would mean the biggest differentiator would be # of hours one puts in, with more hours typically being rewarded, either through higher salary or side job payments (tax benefit?).
I put in an average of 50 hours per week first half of the year and earned enough to make an average rate of $45 per hour.
Do you all consider it part of your job to listen to what's happening in the tech world, learn about personal productivity, etc? If these times were taken out and only time producing tangible output were measured, my average rate would go up, maybe to $70 per hour.
There's also cost of living. I'm not in the bay area, but in another pretty fun and techy place. According to bankrate I would have to make 2.2x to have the same quality of life in The Bay.
My free time is not (currently) consumed with projects. It's consumed by my GF, running, going out, casual reading, a couple TV shows. All this I think is a worthwhile tradeoff. And I need to be away from computer screens after a while!
It would be very interesting to gather people's net pay, hours worked for that pay, and MBTI (ENTJ here), to see what types cluster around what effective hourly rates, what types cluster in terms of total hours, etc.
10pm, usually, and asleep before 10:30 (I've been using the K&R C book + melatonin as a sleep aid recently). 6.5 - 7 hours of sleep seems to be enough for me at the moment.
> Do you ever drink, go out, etc?
Yes, at least once a week I'll see friends and twice a week I'll go out with my wife. If I'm not careful, I can get off schedule, and it often takes quite some time to get back (as in weeks). Those periods when I'm off schedule precipitate bursts of intense productivity (maybe I'm more rested; maybe I'm more motivated).
> I'm asking because I'm a morning person, but I doubt I would enjoy 'getting to it' at 5am everyday.
You nailed it with 'personal time' and a disinclination to work after work hours. I have a few hours of personal time before my wife wakes up where I get to enjoy an activity (coding) that I can't share with her. Any time I spend coding after work hours is time I can't spend with my wife and friends. That time is necessary for me as a human being, and for my work: socializing is good for my brain (promotion of neuronal plasticity and neurogenesis), and breaks are important (recharging and subconscious synthesis + assimilation).
> Do you all consider it part of your job to listen to what's happening in the tech world, learn about personal productivity, etc? If these times were taken out and only time producing tangible output were measured, my average rate would go up, maybe to $70 per hour.
I'm now salaried, and I've stopped thinking in terms of $/hr, and that helps work/life balance, productivity, and attitude.
It's not necessary to learn what other coders are doing, unless I want to be good. Isolation is a straight path to mediocrity.
> It's consumed by my GF, running, going out, casual reading, a couple TV shows. All this I think is a worthwhile tradeoff.
I wouldn't even consider it a tradeoff. Eating isn't a tradeoff to work time -- it's necessary for function. Rest and socializing, too.
I have no idea how many hours a week I "work" for most definitions. About the most I can do is say how many hours I bill a contract client, which is, I hope, ostensibly/approximately how much I work for them. But even then it's not an exact science. I try, but it is arguably impossible to measure with perfect accuracy.
Anybody need some part time product management help? ;)
I have selected 50-60 since I would guess that I end up in the high 50s as an average.
Just sayin'.
Examples: writing code filled of bugs you have to fix later, getting upset on a problem you cannot find a solution for while you could be resting, taking the wrong decision, being cranky, etc.
Agreed, sometimes you have to go beyond the limit, but it's not sustainable.
When I'm feeling the pressure, I just switch to another role.
Try doing smaller weeks, you might be surprised by the result.