How Sleep Deprivation Drives The High Failure Rates of Tech Startups
forbes.com
forbes.com
Recently I had a kid and got to experience the sleep-deprivation effects all over again except this time with one big difference: I work with an awesome team who were able to pick up the slack, and I was smart enough to know when to ask for help (once literally saying "I'm too stupid to do this now, can you do it?")
Sleep-deprivation is going to continue to be endemic in our industry (not just amongst start-ups, the twenty-somethings today are going to be having kids soon themselves). Instead of fighting through the slack, find ways to mitigate it; build your teams with people you can rely on to cover you when you're short.
;)
Sounds agile, right? Pure torture.
I'd skip sleep and coffee before the meeting(s), just to survive them.
Then throw in a pivot every 2 or 3 weeks, involving a new inception deck.
E.g. at home, if I notice I'm too tired to focus on something challenging, I'll do the dishes, or clean the kitchen, or tidy up.
At work, I might tidy the server room, or go through my cron-job folder and investigate all the errors/warnings I've filed away as "annoying but harmless; needs fixing some day" that usually involve fixes that are low risk and easy to verify. Anything that are risky (e.g. requiring changes to a production database server...) I'll defer if possible.
I find a lot of the boring/reptitive tasks are easier to do when I'm tired, as when I'm tired I fall into repetitive routines easily, so as long as I push myself to get started on something repetitive, I'll just keep doing it without getting easily distracted.
> Once upon a time I did the start-up, sleep-deprived,
> living at work thing, and frankly younger me thought
> it was awesome.
Same here. My team recently all stepped back and decided to improve our work-life balance because in the past it had gotten seriously out of whack. Working 16 hour days just doesn't seem sustainable, and I say this as a 20-year-old with a fair amount of energy.... so why is this article being upvoted?
http://www.nature.com/scitable/blog/mind-read/what_keeps_you...
http://www.amazon.com/Uvex-S1933X-Eyewear-SCT-Orange-Anti-Fo...
I cured my insomnia by replacing white compact fluorescent lamps with amber lamps from http://lowbluelights.com. An old comment on this (I have made too many comments here--it's a disgrace!): https://news.ycombinator.com/item?id=6495358
What is also not said is that most manic types also take more extreme vacations. They might take a week off every few months and completely disappear to recharge themselves.
Personally, I need between 8 and 9 hours to be at my best.
http://online.wsj.com/news/articles/SB1000142405274870371250...
It's hard to be stressed when you're sleep deprived. You just say "fuck it, X will work well enough, and I'm too tired to care if it's good enough". Which is probably what you should have done 8 hours ago, but didn't, because you were worried it wasn't good enough.
I find it's just as useful to close your eyes for a minute, and think "I'll probably figure it out later, and I'll still be smart enough to refactor any ugly but pragmatic code when inspiration finally hits" can be just as productive.
As an aside: "my startup" is the new "that novel I'm writing".
> "Burnout is about resentment," she said. "It's about knowing what matters to you so much that if you don't get it that you're resentful."
Is this statement implying that burnout is a psychological condition related to 'resentment' rather then the physical symptoms? I can't help but feel that one could interpret Google's VP as pseudoscience ...
[1] http://it-jobs.fins.com/Articles/SBB000142405270230340470457...
I am fine with chasing a bug for hours every once and then or to extend your schedule when your muse pays you a visit, but if you do it so frequently that it starts impacting your performance negatively, you should stop out of consideration for your colleagues.
When I started working on my idea, I felt guilty when not working. (I naturally don't feel happy unless I'm productive, but this is probably also externally influenced.) In January, I worked 100+ hours. I cooked, ate, slept, went to the gym, but other than that I largely worked. Since I don't consume media entertainment by nature and am an introvert, it was easy to work on my passion unless a friend proactively reached out. I slept-worked a lot, but never felt mentally tired or burned out. Physically though, I became a wreck, at some point tweaking something to the point where I couldn't turn my head. Scary.
I used to think 4 hour work weeks were reserved for those who sought escape from a job they didn't like. But I now realize that the larger goal of work/life balance is equally important for people who love their jobs. And I get that time feels threatening: we have to move fast or the opportunity will pass. But if this idea is something that I'm truly passionate about, I should have no problem devoting a lifetime to it (not blindly treading water without success, of course!).
Now, I know my happiness is still driven by productivity, but I'm trying to redefine that for myself. A day with friends, cleaning the apartment, or climbing at the gym is actually very productive and a good recharge. I really hope more entrepreneurs read this article, and really evaluate what working and living means for them.
FYI I wrote a blarticle about my experience in January and work/life balance here: https://medium.com/entrepreneurs-corner/9461ce206589
http://fixyt.com/watch?v=QfMvqkrQkYQ
Along with the importance of sleep and naps, "creativity is not team sport".
I'm not sure if I ran across this through h/n or not originally, it happened to be in my downloaded videos queue, however.
While some of the arguments in the rest of the article seemed a bit dubious, this opening segment resonated with me—I find myself dreaming in code fairly often, tossing and turning while my brain works through some non-existent problem, iterating non-functional lines of code. It's bizarre, uncomfortable, I don't feel rested and I wake up tense. Generally I take it as a sign that I need to scale back how much of myself I'm sinking in to my work, as I think it's more likely to happen when I've been working longer or later days. I think if I worked in an environment where I was expected to work so much that I started having dreams like this on a more regular basis, I'd burn out or quit very quickly.
As constructed, several far-fetched notions would have to be true to support the conclusion in the way he argued:
- the high failure rate must be due largely to bad ideas and not to poor execution
- sleep deprivation must be endemic at Google, Facebook and Twitter
- Google Glass and Android Wear (and corresponding FB and Twitter projects) must be the product of the sleep-deprived, and shown to be bad ideas (kind of early), and representative of projects at the company.
I think it would be easier to show that lack of sleep just results in poor work. It certainly makes more intuitive sense than honing in on the problem of "crazy" ideas.
I've created over 1000 custom CSS styles over the past 9 months or so fixing various site "errors" such as this. Fixed headers, flyouts, and anything that moves are among the first to go.
What I don’t understand is that if someone is about to faint because he didn’t sleep enough keeps working… Here is a quote that this article remind me of:
"Make rest a necessity, not an objective. Only rest long enough to gather strength." -- Jim Rohn
Oh, and the article does not support the title at all.
(Disclaimer: I wanted this to exist, so I helped Yoni build it.)
I think that sleep deprivation and the high failure rates are connected but not that the causal arrow isn't so simply drawn. People can be well-rested and still have terrible ideas. It might go the other way. It could be that, because these ideas are so terrible, people throw insane amounts of effort behind them to avoid being blamed when they fail. When you have a death march (and most VC darlings are whole-company death marches) you're going to see a split between those who disengage and drop out, and the "A for Effort" strategists who believe that 110-hour work weeks will be noticed above and have them "rescued" (promotion in a big company, EIR gig in VC) when their current project fails. Generally, founders are going to take the "A for Effort" strategy so that, if they fail, they can launch their careers in VC. Employees generally don't have those exit options, but they can't exactly leave before their bosses do in most of these companies.
What we have is an economy of asymmetric risk. Just as hedge fund managers share profits but not losses, and therefore have a higher-risk tolerance than the principals, the decision makers in the VC-funded world benefit disproportionately from obscene risk. Being able to say that one was in Facebook early is career-making for a VC, while 0x and 5x are essentially identical in the personal career calculus.
Founders share some of the risk (they suffer if the thing fails) but at least take part in the upside. Employees get mainly the downside: mediocre equity and no control, nonexistent career support, high risk of job loss and painful hours.
This leads to a risk fetishism (young people! fail fast! sleep is for the weak!) that doesn't make for a good place to work, nor does it produce broad-based success (VC is an underperforming asset class). It produces terrible ideas, reckless business expansion, and the extreme long hours of the startup ecosystem.
TL;DR: the sleep deprivation is a symptom of a deeper problem (risk fetishism arising out of the principal-agent problem in VC).
I often go 30, or more, consecutive hours without sleep when working on certain projects.
No drugs involved, no coffee, just a driving desire to accomplish my goals.
I also sometimes go 2 or 3 days without eating a real meal.
I think I got around 3 hours of sleep last night.