Doing a startup seems to me more like playing soccer than running a marathon. Though you need to pace yourself, there are moments when you want to work super hard. So while being out of breath is not a sufficient condition for winning, it probably is a necessary one. Likewise for startups. Sleep deprivation is not a sufficient condition for winning, but empirically it seems to be a necessary one. Not long-term, obvio…
I'm pretty sure I agree. Certain problems require too much headstate to solve in smaller time quanta, and that at a certain point, when I'm bleary eyed, I lose enough caution to think daring thoughts. Part of it's just the adrenaline, too. And if you have friends goading you on, an allnighter can be pretty fun.
Sleep deprivation is not a badge of honor
31–40 of 45 posts
Re: Sleep deprivation is not a badge of honor
#32Earlier quoted context omitted.
What goes on (that you are allow to share) in those places that requires so much time and energy? I can see building things taking a lot of effort, but is it just for theater that people put in so many hours in those places?
In investment banking, you usually work on a small team of 3-6 people. The work day is very different depending on whether your team is currently working on a deal or is between deals and pitching clients. If your team is on a deal, then there could be honest-to-goodness work keeping your team busy for 100 hours a week. Tasks include preparing the materials used to market your client to potential investors (including…
Re: Sleep deprivation is not a badge of honor
#33Earlier quoted context omitted.
"Sleep deprivation is not a sufficient condition for winning, but empirically it seems to be a necessary one." It doesn't seem to be a necessary one either, given the existence of counterexamples. Eg. Pierre Omidyar started E-bay while keeping his day job and adamantly refused to work more than 8 hours/day on it even after going full-time. One of the reasons he stepped back from a management position was that he didn…
Not everyone in a startup has to work hard, so long as some people do. But someone had to be carrying a pager when the servers went down, or eBay wouldn't still exist.
The article is talking about something completely different: putting yourself in a state of constant sleep-deprivation through working ridiculous hours. And the author is right: that's not half as effective as people claim.
Re: Sleep deprivation is not a badge of honor
#34Earlier quoted context omitted.
I'm pretty sure I agree. Certain problems require too much headstate to solve in smaller time quanta, and that at a certain point, when I'm bleary eyed, I lose enough caution to think daring thoughts. Part of it's just the adrenaline, too. And if you have friends goading you on, an allnighter can be pretty fun.
But taking a slightly longer term view - how is your productivity the next day? What's it average out to over a few days with a big loss of sleep?
The end result is probably only about 20-25 hours work in two days - i.e. not much more than normal working days. The advantage isn't in the total hours, it's in having the same problems rattling around in your head for a long time.
Re: Sleep deprivation is not a badge of honor
#35Earlier quoted context omitted.
Actually, that's how I interpreted it, but I appreciate the clarification. But I still disagree. Anecdotally, I've found that coding for 6 hours a days gets more features implemented and bugs fixed than coding for 14 hours a day. The loss of mental acuity, clarity and creativity (again, this is for me, and anecdotal) is simply too high a price to pay.
Anecdotally, I've found that coding for 6 hours a days gets more features implemented and bugs fixed than coding for 14 hours a day. Sure, in the long term. But when you have a big demo or a customer deadline coming up in 2 days, or a server crashing right now, it often pays to keep working past 6 hours.
I hold up the Schilling's bloody sock as Exhibit A:
Re: Sleep deprivation is not a badge of honor
#36Re: Sleep deprivation is not a badge of honor
#37So trying to extract 110% performance from today when it means having only 70% performance available tomorrow is a bad deal. You end up with just 77% of your available peak. Uh, not quite: x(1.1) + x(0.7) != 0.77(2x). Reminds me of the fuzzy math in DHH's startup revenue calculations...
So as your number of days approaches infinity average work / day approaches 77% of your old work per day. Or on your second day you only get 77% of your normal work day done.
Re: Sleep deprivation is not a badge of honor
#38This might be better titled " Chronic sleep deprivation is not a badge of honor", but the point is well-made. Being sleep-deprived is like being drunk: you're not competent to realize how incompetent you've become.
>This might be better titled "Chronic sleep deprivation is not a badge of honor" The original title is better. It makes perfect sense. It expresses the same meaning. He is clearly referring to the phenomenon of sleep deprivation and not to a single instance. It's clear from the title, and the article even explicitly points this out. He isn't writing legalese. He doesn't have to gird every sentence against being taken…
The first sentence wasn't even my main point; the second sentence was. You write, "He doesn't have to gird every sentence against being taken out of context and nitpicked." Extend me the same courtesy.
Re: Sleep deprivation is not a badge of honor
#39Earlier quoted context omitted.
In investment banking, you usually work on a small team of 3-6 people. The work day is very different depending on whether your team is currently working on a deal or is between deals and pitching clients. If your team is on a deal, then there could be honest-to-goodness work keeping your team busy for 100 hours a week. Tasks include preparing the materials used to market your client to potential investors (including…
Wow. Thanks for the insight. From the outside, I thought the I-bank business was the zenith. Looks a lot like my vision of hell, given that info.
Re: Sleep deprivation is not a badge of honor
#40Earlier quoted context omitted.
Anecdotally, I've found that coding for 6 hours a days gets more features implemented and bugs fixed than coding for 14 hours a day. Sure, in the long term. But when you have a big demo or a customer deadline coming up in 2 days, or a server crashing right now, it often pays to keep working past 6 hours.
Then the injury analogy still holds. I hold up the Schilling's bloody sock as Exhibit A: http://nbcsports.msnbc.com/id/6948862/