Startup Founders Don't Sleep (How many all-nighters do you pull a month?)
gobignetwork.com
gobignetwork.com
Adrenaline can get you through some difficult situations, but in the long run health problems will catch up to you.
I've found from experience -- both while writing code and during my doctorate -- that the quality of work I produce when I'm sleep-deprived drops dramatically. If I'm lucky, I look at my work the next morning, decide that it's garbage, and throw it out; if I'm unlucky, I end up throwing out said sleep-deprived work a few days later, after spending many hours tracking down heisenbugs.
YMMV, of course -- some code is sufficiently straightforward that you can write it in your sleep, or (even better) has sufficiently explosive failure modes that you can test it in the morning and (assuming it doesn't explode) know that despite your lack of sleep, the code is good. And, of course, just as some people can code perfectly well while drunk or high on drugs, some people are entirely unaffected by not getting enough sleep.
But as for me and the code I write? I'll stay away from the drugs and make sure I get enough sleep, thanks.
He forgot to add, "But if I destroy your productivity by convincing you to go sleep-deprived, then I'll be safe."
Would that article make any more sense if it was about olympic athletes?
"I don't sleep, I train. How can I go to sleep when there's so much training to do? While my competitors are asleep and resting, I'm getting in an extra lap around the track. I'll sleep after I get a gold medal."
You just get slower and slower as you stay up, until you're sitting there staring at the screen for 5 minutes before you remember what you're doing.
Any lack of sleep at all will also cost you in productivity the next day. By having discipline to let it be, you can spend 20 minutes on it the next day instead of hours on it tonight and messing up your productivity all day tomorrow.
The hard part is realizing that quality is dropping as quantity increases. It may even be a small drop in quality, but if you add all of those drops up over time, it makes a big difference.
Thanks for informing me that sleep is important.
Paul Graham usually runs his essays by a few people before he publishes them. You might want to start doing the same with your writing.
There's a thread in my comments where people pretty much get it, and then another in the forums where people seem to understand it.
It's good to see the different perspectives.
They didn't get the article with "(How many all-nighters do you pull a month?)" appended to the title.
If you want to stay awake for longer periods and retain mental acuteness, sleep polyphasically.
One of the founders of the consulting firm that I worked for talked about never working past 6 or 7 PM. He never ate out, and spent that time working. You can always work more in your day without sacrificing your sleep and/or health.
At the same time, if we could all survive on less sleep, it'd be nice.
I actually get a little excited when I know I will have a night that I stay up late and get a ton done.
exception to this is when you have a specific deadline that needs meeting and only way to get there is working through the night.
I've done a lot of research on this, through both reading and self-experimentation, and have come to the conclusion that there aren't very many people who would benefit from hacking more than 60 hours a week in short bursts, or more than 50 sustainably. I'd take a hacker who works hard 5 days a week, 10 hours a day, and spends the rest of his time partying over one who sits in front of a computer 12 hours a day, 7 days a week any time.
There's a wealth of information on the topic out there, and studies are published all of the time. It's definitely the sort of thing one should look into when trying to increase their efficiency.
and that is what I got from the article