Live data from Hacker News

A 60-Hour Work Week is Not a Badge of Honour

jeffarchibald.ca

231–240 of 323 posts

Re: A 60-Hour Work Week is Not a Badge of Honour

#231

This false dichotomy is seriously getting annoying. If 60 hours is sustainable for you, do it. If only 30 hours is sustainable for you, do that instead. But stop imposing onto others what is right or wrong when there are so many factors at play. Some of my most productive memories are summers studying and working for 12 hours a day, 6 days a week (= 72 hours). I didn't get tired, burned out, or anything. Another summ…

Indeed... And most of the friends around me who made it big also played it hard. When Broadcom was nowhere several employees number xxx (with xxx less than 300) were, while in crunch-mode, sleeping in their trucks , on the parking lot, to deliver chip plans on time. Stock options have been good for them the day Broadcom was worth $12bn. I've got a few friends who started a 3D-rendering business for TV ads, short movi…

And I know even more startups that worked 100+ hours and got nowhere. Simple logic would then tell us that amount of work is inversely correlated with productivity!

The actual truth is that success is more about luck than anything else. Working 100 hours a week is just you killing yourself without increasing the probability of success more than, say, getting a better-connected CEO would.

Re: A 60-Hour Work Week is Not a Badge of Honour

#233

Earlier quoted context omitted.

Its even easier to fool yourself into thinking you can't handle things that actually can handle. I don't know if that's true or not. It's probably too vague to be even true or false. But it also seems like a dangerous sort of symmetry to invoke because the consequences of going beyond your capacities tend to be a lot worse than the consequences of not quite reaching them. I recall you as fitness person from other dis…

I guess if there are negative consequences and you aren't able to detect them and respond appropriately, then you'd not attempt anything. Its too dangerous for you.

I'm saying that someone is going to attempt something that pushes them to significant physical limits, they need to have good controls. Feeling like you can do something should be supplement by some understanding.

When I teach stretching and movement, I advice my student to only go to the edge of their "comfort zone" at any one point and I only teach certain stretches. It's known that most people's limberness can be gradually increased so that's relatively safe.

It's pretty well known (see studies on this page) that most people can't "learn" to go without sleep and I wouldn't advice them to try to do so (the point of the article).

And I can believe a few people who in the right place at the right time and brutally push themselves can get rich, rich, rich. That doesn't take away from the point of most people who work with extended years of sleep deprivation screwing themselves up (and this can include a fair fraction of the first group).

Sure, push yourself to greatness. I like to push the quality of my activity, not the quantity anyway.

Re: A 60-Hour Work Week is Not a Badge of Honour

#234

I still find it a bit odd that the 3-day week before I go on vacation is probably my most productive, focused week. It probably has to do with focus and weeding out the distractions with the "I need to get this done by Weds night, so can we talk when I get back?". I've worked a sustained 60 for a lot of years and done back-to-back 80's. I just don't think I was super productive. My most personally productive run was…

"My most personally productive run was on a job that I had 4 hours in the morning to program and was doing something completely different in the afternoon."

I totally agree with you. If you super concentrated on solving one hard problem within 4 hours in the morning, it's hard to have the same amount of energy to do another on in the rest of the day. So we need to manage our productivity in a better way to balance the work load and intensity. We need to have time to get recharged.

Re: A 60-Hour Work Week is Not a Badge of Honour

#235
Kudos for writing about this. So many people in the startup world like to brag about how they do things without a whole lot of evidence to back them up. Usually it is about some cool tech that they use, but as you point out, the long hours meme is also something that is going around like a virus even though there is no evidence that it does any good.

There is a lot of talk about big data in our industry, but it seems to me that some small data experiments would be useful as well because there is so much that we do with no data to back up the practices.

Re: A 60-Hour Work Week is Not a Badge of Honour

#236

This false dichotomy is seriously getting annoying. If 60 hours is sustainable for you, do it. If only 30 hours is sustainable for you, do that instead. But stop imposing onto others what is right or wrong when there are so many factors at play. Some of my most productive memories are summers studying and working for 12 hours a day, 6 days a week (= 72 hours). I didn't get tired, burned out, or anything. Another summ…

I agree that developers should not try to work more than 40 hours per week on a regular basis.

But when I was younger, I went for years working around 16 hours per day, 7 days per week and everybody thought that I was a rockstar genius. But it was not all mental work. I probably spent about 8 hours a day on software development and then I wehnt home and worked another 8 hours in my half acre of gardens, 3 acre asparagus field or shoveling the daily snowfall of 6 inches or so, off my 100 yard driveway. Not to mention sawing and splitting a few cords of firewood to heat the house, cutting Christmas trees to sell.

The physical work was energizing after a day spent writing software, and the mental work was energizing after all the physical labor that I had done the day before. I'm not saying that the physical labor made me more productive at developing software, although that may be true. But I think that when people count hours and then try to use that to prove a point, they forget to classify what is being done in those hours.

Case in point. When I have a tough coding problem, I don't slog away at it for extra hours. I go sit in a different chair, stare out the window, look at the cloud shapes, then close my eyes and think of absurd ways to solve the problem. Now if I would include that time in my count of hours per day and tell you that I can regularly put in a 10 hour day, you would be misled. The total hours are not as important as what you do with those hours.

If you are going to play on the net for 20 hours a week, then yeah, you may need to put in a full 60 hours. Or you could stop goofing around and do your work. Pay attention to your productivity. Split your day into chunks, take your coffee and lunch breaks. I used to join the smokers on their smoke breaks even though I didn't smoke because it got me out of the chair, moving around, and I got to stand in the fresh air and sunshine (upwind of course). And I almost always go for a walk at lunchtime. This is not a waste of time. These pauses are essential for you to get your maximum mental effort.

Sure, sometimes you get stuck into a problems and go for hours without leaving the chair. Even if you are 50 you can do that once in a while if you eat healthy (read Joel Fuhrman), but the key here is "once in a while". Once in a while you can pull out all the stops, but like heroin, it does not get better by doubling the dose.

Buddha had it right when he said (and I paraphrase him) "All things in Moderation". It takes great discipline, but discipline is what software developers need to cultivate in themselves.

Re: A 60-Hour Work Week is Not a Badge of Honour

#237

Earlier quoted context omitted.

Indeed... And most of the friends around me who made it big also played it hard. When Broadcom was nowhere several employees number xxx (with xxx less than 300) were, while in crunch-mode, sleeping in their trucks , on the parking lot, to deliver chip plans on time. Stock options have been good for them the day Broadcom was worth $12bn. I've got a few friends who started a 3D-rendering business for TV ads, short movi…

And I know even more startups that worked 100+ hours and got nowhere. Simple logic would then tell us that amount of work is inversely correlated with productivity! The actual truth is that success is more about luck than anything else. Working 100 hours a week is just you killing yourself without increasing the probability of success more than, say, getting a better-connected CEO would.

There really is an opportunity here for someone to collect some real data on this and help us learn just how far you can push it and for how long. There are so many startups in SV that someone who lives there could interview people at these startups, every 3 months, collect the data, and then after a few years we would have some evidence that suggests the general expected result.

There will always be some outliers, but remember, some startups who have done everything wrong, still made it big. Single examples here and there are not data. It's hard work to get real usable data, but chances are some of you know people at Berkeley or Stanford who would be into that sort of sociological/psychological research.

Re: A 60-Hour Work Week is Not a Badge of Honour

#238
What 60hr/week worker is asking for a badge of honor? Do you really think that a Badge of Honor and pride is why they are working all these hours? I have never seen this in all the startups that I have worked at.

In my personal observations there are three reasons that people work long hours. Money, self advancement (skill wise or other) and a loyal commitment to finish a large task within a time span.

Re: A 60-Hour Work Week is Not a Badge of Honour

#239
post #166

Earlier quoted context omitted.

>> falsifiable evidence ("testable against the empirical world") > That's not what falsifiable means. You truncated the original, cut out an essential word, then argued against the edited version. Here's what I said: > Because psychology's topic is the mind, and because the mind is not a physical entity, psychology cannot produce empirical, falsifiable evidence ("testable against the empirical world") to supports its…

OP is incorrect that psychology is not a science. The remainder of the discussion is quite tedious, and shows that the OP has a very confused notion of mind body separation (hint, by and large they are not, whether you're a dualist an epihenominist or something else - I tend to something else but wouldn't feel confident to write my viewpoint down). What is correct is that experimental designs are more or less not pos…

> OP is incorrect that psychology is not a science.

Pretend to be a scientist and post your evidence. Here's mine -- the director of the NIMH has recently ruled (http://www.nimh.nih.gov/about/director/2013/transforming-dia...) that the DSM (psychology's "bible") may no longer be used as the basis of scientific research proposals, for the simple reason that it has no scientific content. The director went on to say:

"The goal of this new manual, as with all previous editions, is to provide a common language for describing psychopathology. While DSM has been described as a “Bible” for the field, it is, at best, a dictionary, creating a set of labels and defining each. The strength of each of the editions of DSM has been “reliability” – each edition has ensured that clinicians use the same terms in the same ways. The weakness is its lack of validity."

"Unlike our definitions of ischemic heart disease, lymphoma, or AIDS, the DSM diagnoses are based on a consensus about clusters of clinical symptoms, not any objective laboratory measure. In the rest of medicine, this would be equivalent to creating diagnostic systems based on the nature of chest pain or the quality of fever. Indeed, symptom-based diagnosis, once common in other areas of medicine, has been largely replaced in the past half century as we have understood that symptoms alone rarely indicate the best choice of treatment. Patients with mental disorders deserve better." [emphasis added]

There is often an embarrassing degree of self-reference in discussions where psychologists try to claim that psychology is a science. The defenders invariably see no need to produce evidence for their claim, as though evidence is irrelevant in a discussion of science. And for a typical psychologist, saying psychology is a science is expected to end a conversation, whereas for a scientist, that claim can only begin a conversation in which evidence rules.

> Next up we have this whole notion of falsifiability. It's a red herring.

Only if science isn't defined as it is in the law -- which it is. Science-defining laws are on the books to keep Creationism out of public school classrooms, and while crafting those laws with the assistance of expert witnesses, guess which non-negotiable criterion always appears in the final ruling? Falsifiability.

Here is one such ruling (http://www.talkorigins.org/faqs/mclean-v-arkansas.html) -- science must have these properties:

1. It is guided by natural law;

2. It has to be explanatory by reference to natural law;

3. It is testable against the empirical world;

4. Its conclusions are tentative, i.e. are not necessarily the final word; and

5. It is falsifiable.

I bring up this law to make perfectly clear that falsifiability, empirical evidence, and the other standard requirements for science, are only red herrings to people who think they can define science any way they please. For a scientist, obviously this kind of argument is unnecessary -- they already understand what science requires.

> What is correct is that experimental designs are more or less not possible in behavioural psychology.

Wait, what? Because one cannot design reliable experiments in psychology, therefore psychology is scientific? On what basis -- that real science is too difficult?

> This could be OP's second point of confusion.

The only confusion is yours.

Post reply on HN