mirror of
https://github.com/wezm/wezm.net.git
synced 2024-12-18 18:29:54 +00:00
Add polyphasic-sleep-schedule
This commit is contained in:
parent
57abdefef2
commit
56f93f1e4f
2 changed files with 75 additions and 0 deletions
64
content/personal/2011/01/polyphasic-sleep-schedule.html
Normal file
64
content/personal/2011/01/polyphasic-sleep-schedule.html
Normal file
|
@ -0,0 +1,64 @@
|
|||
I've lamented the amount of time dedicated to sleep for many years now. There's
|
||||
evidence of it as far back as 2001 where I included the following ["moto" on my
|
||||
home page][moto]:
|
||||
|
||||
> "Sleep is the single biggest waste of time in life. Avoid it at all costs."
|
||||
|
||||
[moto]: http://web.archive.org/web/20010428064609/yallara.cs.rmit.edu.au/~wmoore/cgi-bin/index.cgi
|
||||
|
||||
I have lots of things that I'd like to do but due to the amount of time that
|
||||
work and sleep occupy only get an hour here and there.
|
||||
|
||||
Around 2004 when I started working full-time I read about what is now known as
|
||||
the Uberman sleep schedule. Under this sleep schedule all sleep is replaced by
|
||||
six 20 minute naps across the 24 hour day. This sounded great but the schedule
|
||||
had to be strictly stuck to and I didn't have an employer at the time that
|
||||
would be ok with me taking naps through the work day.
|
||||
|
||||
Fast forward to last week during our weekly Monday meeting. My current boss,
|
||||
[Matt][matt], announced he was going to start the Everyman 3 sleep schedule. In
|
||||
this modified variant of the Uberman schedule there is a 3 hour core sleep and
|
||||
three 20 minute naps distributed across the day. The inclusion of the core
|
||||
sleep seems to provide a bit of flexibility in the required nap times
|
||||
potentially allowing them to taken up to an hour either side of their scheduled
|
||||
time.
|
||||
|
||||
[matt]: http://twitter.com/#!/matthewfallshaw
|
||||
|
||||
So with Matt starting a sleep schedule and me now working for a [nap friendly
|
||||
company][trike] I've also decided to give the Everyman sleep schedule a try. My
|
||||
schedule is as follows:
|
||||
|
||||
[trike]: http://trikeapps.com/
|
||||
|
||||
<table class="left_headers">
|
||||
<tr>
|
||||
<th>Core Sleep</th><td>11pm - 2am</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Nap 1</th><td>7am</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Nap 2</th><td>12pm</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th>Nap 3</th><td>5pm</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
The way the sleep schedule works is that initially you become so sleep deprived
|
||||
that at each of the nap times your body decides it best make the most of the 20
|
||||
minutes of sleep it has available to it and skips the usual sleep phases and
|
||||
jumps directly to the R.E.M. phase. R.E.M. sleep is what is mainly responsible
|
||||
for recharging and fending off tiredness. Its also been reported that by
|
||||
getting R.E.M. sleep across the whole day you wake up feeling really switching
|
||||
on and alert and therefore potentially more productive. Wikipedia has a [good
|
||||
summary on polyphasic sleep][wikipedia].
|
||||
|
||||
[wikipedia]: http://en.wikipedia.org/wiki/Polyphasic_sleep
|
||||
|
||||
Of course there is an adaptation phase for the schedule, which can be a couple
|
||||
of weeks or more. As mentioned this basically involves driving yourself to
|
||||
exhaustion to trigger R.E.M sleep in naps. Tonight is my first night on the
|
||||
schedule so I'm in for some rough days ahead. I aim to post weekly updates on
|
||||
my progress.
|
11
content/personal/2011/01/polyphasic-sleep-schedule.yaml
Normal file
11
content/personal/2011/01/polyphasic-sleep-schedule.yaml
Normal file
|
@ -0,0 +1,11 @@
|
|||
---
|
||||
title: Polyphasic Sleep Schedule
|
||||
extra: I commence a polyphasic sleep schedule in order to reduce my daily sleep to 4 hours per day.
|
||||
kind: article
|
||||
section: personal
|
||||
created_at: 2011-01-20 02:18:00
|
||||
keywords:
|
||||
- sleep
|
||||
- polyphasic
|
||||
- schedule
|
||||
short_url: http://bit.ly/e4AgMh
|
Loading…
Reference in a new issue