Live data from Hacker News

How do you make programmers work 60-80 hours per week?

brianknapp.me

151–160 of 200 posts

Re: How do you make programmers work 60-80 hours per week?

#151

When I really like the work that I am doing and there are some real challenges, I can get up to 6 hours of work done before I have to take a break for a few hours. Not every day, but 2-3 days out of 5. It means that there is no point in making an appearance before 10 am or working past 4 pm. But when I am really smoking I can put in another 2-4 productive hours in the evening after 7 pm or so. Of course, few employer…

Funnily enough this is how athletes work. Most athletes start with a 2-3 hour session, then eat, ideally nap, and then a second 1-2 hour session at a low intensity.

Re: How do you make programmers work 60-80 hours per week?

#152
post #138
post #11

I seem to be alone in this, but I actually do about 25-30 hours of actual programming work each week. And that's sit-down-and-concentrate-and-build-shit work. I'm pretty ruthless about declining extraneous meetings and I keep my door closed most of the time. I think it's reasonable to have 25% of a 40-hour week be for meetings, helping other people, eating lunch, sitting in on interviews, and learning/trying out new…

Do your worst, skeptical HN, but I swear on my life I've been maintaining more than 80 hours of ridiculously productive, focused coding time per week, for about a year. It so different when you love and believe in what you're working on. I literally can't wait to get out of bed and start working, and the entire day goes by before I notice. The thing I'm working on is a sheer joy to work on, and the conditions are ide…

Do you have a family?

Re: How do you make programmers work 60-80 hours per week?

#153
post #138
post #11

I seem to be alone in this, but I actually do about 25-30 hours of actual programming work each week. And that's sit-down-and-concentrate-and-build-shit work. I'm pretty ruthless about declining extraneous meetings and I keep my door closed most of the time. I think it's reasonable to have 25% of a 40-hour week be for meetings, helping other people, eating lunch, sitting in on interviews, and learning/trying out new…

Do your worst, skeptical HN, but I swear on my life I've been maintaining more than 80 hours of ridiculously productive, focused coding time per week, for about a year. It so different when you love and believe in what you're working on. I literally can't wait to get out of bed and start working, and the entire day goes by before I notice. The thing I'm working on is a sheer joy to work on, and the conditions are ide…

Sounds great. But how many years will that carry on for? Surely whatever you're choosing will be complete in the next month or two of 80 hour weeks?

Re: How do you make programmers work 60-80 hours per week?

#154
post #42

Earlier quoted context omitted.

You're not alone. I, and everyone at work except perhaps our CEO, get probably 30 hours of focused programming done, with the caveat that probably around 75% of that programming is done in pairs. Which still feels like very productive programming most of the time. We do this by using the pomodoro technique and TDD (although I'm sure there are lots of other ways, and that it's mostly a combination of company philosoph…

I've always liked pairing because it ensures that you're both there to get the thing done, and generally I've found that it keeps both of us from goofing off (until the thing is done, then it's time to play). While the theoretical throughput would be 50% (two people doing one thing), it ends up being greater than if we had both tried to work on different things, since the one thing we're doing comes out better since…

I used to do the same as a defence contractor. We coded in a team of two, or sometimes with a third wheel who was learning. About 1.2x more productive, but rewrites and dead ends became rare.

Re: How do you make programmers work 60-80 hours per week?

#155

Earlier quoted context omitted.

What's your point? They are talking specifically about students a.k.a people who are literate and have a degree. How's citing literacy or poverty statistics relevant?

India has real problems. Needing to take out a large loan to get a tertiary education when you have completed secondary education in a country where a quarter of the population are illiterate is not a problem. The money that is spent on making education free for students at a tertiary level could be spent on improving primary education and it should be. No state in India is as rich as Ireland was in 1970. That's arou…

No, it is how you build a functioning economy. If the graduates bring in money to the country, it is taxed, and that tax per year is far more than an unskilled slum dweller will likely see in toto in their life. Raising everyone to the level of a 5th grade reader wouldn't give you an economy that brought in money, and you'd never progress.

Re: How do you make programmers work 60-80 hours per week?

#156
post #138
post #11

I seem to be alone in this, but I actually do about 25-30 hours of actual programming work each week. And that's sit-down-and-concentrate-and-build-shit work. I'm pretty ruthless about declining extraneous meetings and I keep my door closed most of the time. I think it's reasonable to have 25% of a 40-hour week be for meetings, helping other people, eating lunch, sitting in on interviews, and learning/trying out new…

Do your worst, skeptical HN, but I swear on my life I've been maintaining more than 80 hours of ridiculously productive, focused coding time per week, for about a year. It so different when you love and believe in what you're working on. I literally can't wait to get out of bed and start working, and the entire day goes by before I notice. The thing I'm working on is a sheer joy to work on, and the conditions are ide…

I love and believe in what I am working on, I usually can’t wait to get out of bed and start programming, and that’s exactly why I force myself to stop after a reasonable number of hours. Because I know 80 hours a week (or 40 hours a week) of programming would not be sustainable for me. That much work would simply destroy my life outside of work and harm my productivity at work. Short-term gain, possibly, long-term loss, inevitably.

Re: How do you make programmers work 60-80 hours per week?

#157
post #111
post #11

I seem to be alone in this, but I actually do about 25-30 hours of actual programming work each week. And that's sit-down-and-concentrate-and-build-shit work. I'm pretty ruthless about declining extraneous meetings and I keep my door closed most of the time. I think it's reasonable to have 25% of a 40-hour week be for meetings, helping other people, eating lunch, sitting in on interviews, and learning/trying out new…

You have a door: there's your 50% productivity boost.

The cynical side of me interprets this as: you can leave if you don't like it.

Re: How do you make programmers work 60-80 hours per week?

#159
post #138
post #11

I seem to be alone in this, but I actually do about 25-30 hours of actual programming work each week. And that's sit-down-and-concentrate-and-build-shit work. I'm pretty ruthless about declining extraneous meetings and I keep my door closed most of the time. I think it's reasonable to have 25% of a 40-hour week be for meetings, helping other people, eating lunch, sitting in on interviews, and learning/trying out new…

Do your worst, skeptical HN, but I swear on my life I've been maintaining more than 80 hours of ridiculously productive, focused coding time per week, for about a year. It so different when you love and believe in what you're working on. I literally can't wait to get out of bed and start working, and the entire day goes by before I notice. The thing I'm working on is a sheer joy to work on, and the conditions are ide…

You need to be thinking of a career of 30+ years rather than a 3 year sprint.

It's cool you're spending your time producing, but don't forget you need to take care of yourself and hone your fundamentals (linear algebra, data structures, algorithms, your field).

Re: How do you make programmers work 60-80 hours per week?

#160
post #159
post #138

Earlier quoted context omitted.

Do your worst, skeptical HN, but I swear on my life I've been maintaining more than 80 hours of ridiculously productive, focused coding time per week, for about a year. It so different when you love and believe in what you're working on. I literally can't wait to get out of bed and start working, and the entire day goes by before I notice. The thing I'm working on is a sheer joy to work on, and the conditions are ide…

You need to be thinking of a career of 30+ years rather than a 3 year sprint. It's cool you're spending your time producing, but don't forget you need to take care of yourself and hone your fundamentals (linear algebra, data structures, algorithms, your field).

Well... As pg mentions in one of his essays: the startup game is about getting the rewards of a 30 year career out of 4 years. If you truly believe that you are building something that matters and you are going to win, 80 hour weeks make a lot of sense.
Post reply on HN