Poll: How many hours do you work a week? | Hacker News Reader

Poll: How many hours do you work a week?

60 pointsInfinityX063 comments

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.

View on HN

I just pulled up the last year's worth of consulting invoices and yes, it looks like I managed to bill an entire 40 hours once in the last 52 weeks.

I have a personal policy of only billing for the time I'm creating value. So if I boot up, fire up the IDE, sip my coffee, pull up a bug report, then proceed to browse f'ng Hacker News for 2 hours, I don't charge my time. Similarly, if I notice by lunchtime that I'm just plain not smart enough to program computers for money today, I'll stop the clock and go climbing or something.

So yeah, I bill 20-30 hours each week, but they're good hours. Back in my salaried days I'd often find my butt in the Aeron for a good 60 hours a week, much of which was spent debating where to go for lunch, reading the internet, and maintaining the corporate HalfLife server. I doubt I got any more productive hours in then than I do now.

Exactly. I've had a similar experience consulting, and wondered if it was the same for others... or if they're just loose with counting hours.

The only time I've been able to rack up more than 20~25 hours is when I work at the client's office (as I've been doing for the past couple of months).

I do the same, good man.

back at d-cibel industries, i only worked something like 10 hours a week.

I also started billing this way earlier this year and it has helped me focus. Now if I get distracted while I work I feel like I am wasting time, and know I am not going to be rewarded for it.

So, true. I too do the same.

I reliably put in four or five 50+ hour weeks per year (especially if I'm at a new startup), but I've learned through hard experience that it's unbelievably counterproductive to do that for longer than a week or two at a time. My personal life and ability to stay awake, much less think/code clearly, suffer otherwise.

Of 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.

yeah. what I find interesting is that while most people seem to claim 40-50 hours, they don't appear to be working as much as people I know who track their hours (and don't count breaks) who have a difficult time reaching 40 hours a week.

I suspect most people inflate the number of hours spent working (or count things like hacker news as work.)

I think most people that have a 9-5 and do a small amount of after-hours contracting, or regularly stay a little bit late to finish something up will be voting 40-50. That's how I voted, even though if you subtract slacking time and lunch, I probably clock in under 40 hours most weeks.

This would seem likely to encompass the majority of HN's readership, startup crowd aside.

When you bill per hour, its harder to reach that number. This is misleading because salaried employees and equity holders can easily work many hours, but hourly workers are limited by how many hours their employers will allow them to work (or by how many hours contractors can invoice their clients)

I checked 80+, but it depends on how you define work. A lot of work is sitting around in an all-night diner drinking coffee and drawing on napkins. It ain't such a bad thing, and is probably less stressful than playing a first person shooter.

Agreed, it depends on how you define work. I spend most of my waking hours in front of a computer, and a lot of that is building something - though it may not always be paying client work. I really have no idea how many hours I "work".

When you are working on your own startup, you don't see it as work. It's easy to "work" many hours, but it's enjoyable to a great extent.

Or even your own projects. I have day job, I'm finding a few hours every day to write open-source, and I'm finding a couple of days of extra time a week to work on my startup. Hard work? Yes... But I only see the day job as actual work, and that's only when I'm not working on something interesting.

Programming is awesome, especially in Perl :D

I used to perl but now I python :)

It'd be interesting to cross-reference this with number of posts and hours spent opining about every goddamn thing on HN.

Just sayin'.

That would be a great little data mining project!

Since I use the RSS I only spend an hour at most a day reading stuff on here, but I work a ~40 hour week usually.

Most days* :

5:00am - 10:00am

  * OS development
  * puzzles
  * articles
  * work on personal projects

10:00am - 6:00pm

  * coding for my day job

13hr/day * 5 days/week = 65hrs + anything I can sneak in on weekends

I 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.

But you listed "puzzles' in your work, and you included your lunch and co-worker conversation time, unless you're always in front of your screen, zero distractions. If we're all counting all that time, then that changes these numbers a lot. We really need to clarify what 'work' is for these numbers to be useful, at all.

There was an episode of 'The Office' where Jim took note of any time Dwight wasn't working. Dwight stops using the restroom in favor of a bottle beneath his desk. He keeps his eyes open while sneezing to keep them focused on his computer screen.

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.

What time do you go to bed?

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.

> What time do you go to bed?

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.

When I really want to be productive 20-40. When I really need to get something done which requires too much stupid human time, 50-60.

I have a F/T+ day-job where I work for one company 30-40 hours a week (it's supposed to be about 20) and am on loan to another company about 25 hours a week. Then I come home and work on my Startup with my co-founder 2-3 hours a day and full days on most weekends...about 20-30 hours a week. So I usually put in 60-70 hour weeks on the low end.

Recently a co-worker had to take an extended leave of absence and my hours at my main company ballooned to full-on 50-60 hours + the 25 hour side job + the startup. Needless to say my startup work had to take a reduction in hours with my co-founder flying solo for a bit (which was hard on her because we just got a bunch of coverage on killer startups, feed my app and a ton of Spanish language tech sites). But for a couple of months I was pulling 90-100 hour weeks.

My co-worker has returned and my weeks have fallen back to their regular 60-70 hour pattern.

My own experience is that above 50 hours you start destructing value, not creating some.

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.

I only agree with you if you so the same work for those 50 hours. If you work for 80, but this is split between marketing, coding, networking and strategy then its not the same thing.

When I'm feeling the pressure, I just switch to another role.

I see what you mean, but 80 hours means more than 11 / day without any rest. Not sustainable.

Try doing smaller weeks, you might be surprised by the result.

Like that idea, but I'm working a day job and then my business. Not sure I can !

Your body and psyche don't care what sort of excuses or goals you have for it.

Yes, but networking and marketing is not even close to as taxing as coding or solving mathematical problems. This is so much the case, that I generally discount business dinners as not work.

That depends on your proclivities and the natural bent of your personality. Networking and marketing may not be as intellectually taxing as coding, but they can be physically and emotionally taxing when done in person for significant amounts of time. Of course, if you regard business dinners and networking as enjoyable, they won't seem as taxing!

My brain works about 80 hours a week, but my fingers work about 30.

At the startup I work at, I average around 60 hours a week, with many weeks exceeding 70 hours a week. This is also usually done in a 5-6 day work week.

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.

What gets defined as work? That is where it gets fuzzy for me. First thinking about work related issues starts at 6am, is interrupted for a couple hours with getting kids to school, then back at it until 6pm, break for dinner and spending time with the family, and then back to work thinking until bed - about 10pm. I have been self employed most of my life and all of my children's lives. So this fragmented work schedule is normal to me. I generally work 6 days a week, sometimes only 5, and have noticed that if I work more than about 17 days straight I start to get really grumpy.

I have selected 50-60 since I would guess that I end up in the high 50s as an average.

Well.. I work for a large international IT-consulting corporation at a client site. I go to work at 8 AM and leave around 4 PM. So this makes.. umm.. 40 hours per week. During normal 8 hour office day I usually attend meetings for around 1-2 hours, chat around with fellow consultants and client personnel for 2-3 hours, solve client issues alone or with colleagues for 1-3 hours. For the rest of the day I drink coffee and read HN + other web sites.

Yes - I feel sometimes that my job is somewhat boring and that I should be doing something more "activating" but I: - get reasonable salary - do my job very well - have great work/life balance

So maybe there is not so much to complain.

Hiring?

I put 40-50 hours as real client work + essential other activities (finances, website work, etc) but in reality as a small business starting out I never stop thinking about what next to do with my company.

40 at day job, 40+ on consulting projects. Finding it harder to keep up the pace and want to reshuffle to find time for my own projects. Hard to get off that consulting gravy train though.

Damn do I know what you mean. I pull 20+ on consulting but it's getting to the point where it's affecting my health.

I'll stop soon, probably go full time consulting so I can actually have a life.

Best of luck.

I currently work about 20 hours a week on my day job, 10 hours a week freelancing, another 20 hours day-dreaming about my own startup and reading Hacker News/Techmeme/Reddit.

I work 4 days a week so that makes 32 hours and try to fill my friday with small jobs on the side so between 32 and 40, never over that. I cherish my personal life way too much to work more than 40 hours per week. I don't even receive work e-mails on my phone neither do I check them when I'm not at work. I like to keep this separation as clean as possible so that when I'm off work, I don't think about work and / or stress about stuff going on at work.

"How many hours do you work a week?"

Weird question. "How many non-sleeping hours a week do you not work?" would be more like it.

After all, if you're having a blast, does it really count as work?

I work 27 hours a week, at home. I usually make a full day when I go grab some coffee at the office and talk to my colleagues, because otherwise I wouldn't get anything done on those days. So effectively that's about 4 hours a day. Of course I can just squeeze in more hours if I have an interesting task at hand; then I can just keep the following day off (except checking email occasionally, that's no problem).

Well, i had the doubts and started using rescuetime(www.rescuetime.com) for tracking my activities. I won't get into definition of work but just give some stats. i clock between 50-70 hrs a week on the computer. Productive time(Defined as time spent on the terminal/editor) : 20-30 hrs. Rest is either browsing blogs/email/video..:) P.S: And oh, am dissatisfied with what i have accomplished.

We appreciate you RescueTiming! If you have any questions you can reach me at jason@ - rescuetime.com.

As a startup co-founder do about 10h/week doing stuff I wouldn't otherwise do for free (mainly, recruiting, admin, contracts, and driving to meetings). I spent about 100h/week doing stuff which is fun and which I'd do for free (hacking on stuff, talking to people about stuff, reading and learning about what I'm working on, etc.)

If you asked me a few months ago I would've said 60-70 but since I started time tracking I've found it's only 40-50 hours on average. This is with being strict about what's considered work time (meals, "general research", etc. are all off the clock)

Remember there is often a difference between working hard and working smart. I would try to focus less on the amount of hours put in and instead just focus on what value you're adding to your project.

Generally speaking, I do less than 20 hours of paid client work per week. On the other hand, I spend a significant amount of time reading CS material and working on personal projects.

It depends. I work fulltime so 37.5 hours a week but then I do more from about 7pm till midnight or later. Then theres the weekend where I probally do 48 hours over a month.

I'd say about 34 right now, once you account for occasional distraction. I usually have trouble focusing (on anything) for more than 3 or 4 hours at a time without a break.

I work 8am to sunset on weekends as a skydiving instructor. During the week I do remote stuff for a few companies for about 4-5 hours a day. I try take off 1 day a week.

Officially I'm contracted for 37.5 hrs/mo but I stay 1-2 hours more most days. I'm a student on a industrial placement so I might as well make the most out of it

Officially 40 (slightly more if reading HN at work counts) until the end of tomorrow. After that, 0 until I've moved and found a new job etc.

Working full time at a startup and doing part time contract work to help cover the bills.

Anybody need some part time product management help? ;)

http://hackernewspoll.appspot.com/2843979

25-30 consulting, 5-15 open source, 5-15 skill maintenance/hacker news/researching/learning

I work all the time. In fact, I'm not sure I know the difference between work and leasure.

Am I sick? :p

I work 40 at my day job, then I easily put another 40+ into my startup.

define "work" for purposes of this poll. work at job? work at job + side projects? work around the house? does commute time count? any hours inside an office as an employee, including reading email or chatting at coffee machine? time spent fleshing out ideas in the shower or mulling over difficult problems on a walk?

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.

I hope I have a project some day where I find myself wanting to work anything more than 40 hours a week. I have very modest living requirements and would be more than happy on whatever I could make working 25-35 hours a week. Of course, I'm not counting personal projects, my own learning or whatever. But 80 hours? That sounds (in a non-judgmental way), depressing.

Since I quit my job I've been working more than twice as much and loving it (on my startup). I ran into a problem after about two weeks with my eye twitching from too much screen time but took a week vacation and have been fine the two months since. I now sit by a window so I occasionally glance out and exercise my eye focus muscles.

Reply on news.ycombinator.com