Misadventures in sleeping

My enemy, nighttime

Starting from a really early age, I had difficulties sleeping. Let's call these difficulties insomnia on steroids. I couldn't fall asleep, and when I did, there was no way I could stay asleep. It impaired my life so much, that I would frequently fall asleep at various points during the day out of sheer exhaustion.

Words like narcolepsy were thrown around. Those sleeping pills that are supposed to be a temporary fix looked like they might become a permanent fixture.

So, my parents did the reasonable thing, and took me for a sleep study. I got all wired up and was told to go about my normal routine. As if there's anything normal about tripping on wires connected to every square inch of you. I don't remember much about the actual study, except that thoughts like this is stupid kept drifting through my mind.

REM sleep, absent visitor

The results came in. I didn't have narcolepsy or really any sort of definable sleep disorder. What I did have was an extraordinarily low occurrence of REM sleep. This explained quite a bit -- including why my involuntary naps during the day were plagued by vivid dreams.

There wasn't much they could do about it, though.

I went about my life, trying different techniques to cope with my strange sleeping patterns. I tried meditation, implementing routines, deep breathing, sleeping on my left side, creating pitch black rooms, and various pharmaceutical assists. Nothing really worked, but at least I was able to stay awake during the day and become a productive member of society.

The lesson, 20 years coming

At some point, I gave up on this ridiculous notion that everyone needs eight hours of sleep. The NYTimes ran an article that helped me come to terms with the idea that I wasn't a failure if I got six hours. I even found out that my migraines were even tied to getting too much sleep!

My life improved. I regularly get around 4-7 hours of sleep a night. I go to bed whenever I want, usually around 1am, never before 10pm. My goal is to get up at 6:30am. I stopped tying my self worth to how much sleep I managed to get (when did that even happen, anyway?).

Courtesy of fitbit, insights

Over the holidays, I purchased a fitbit. Like a true geek, I wanted data on my typical activity levels before attempting to improve them. So far, it's worked well -- and I do enjoy the gamification of my health.

I didn't anticipate the data that fitbit gave me on my sleeping habits. On a whim, I decided to try collecting data for a week, before trying to examine it. I'm not sure how it calculates the sleep efficiency score, so I generally disregard it. I don't take what the reports say as gospel, but as an estimation.

What I found surprised me. I always thought that it took me at least 45 minutes to fall asleep, but fitbit reported that my average time to fall asleep was 15 minutes. Yes, I had periods of restlessness during the night, but they were nowhere nearly as frequent as I had thought (~9 times). The only thing that didn't surprise me was how much time I spent asleep -- it falls squarely in that 4-7 hours per night range.

I'm tempted to have another sleep study done, to see if I've managed to correct my REM sleep deficit in the last 20 years.

By way of technology, comfort

I had achieved an uneasy peace with my sleeping habits before fitbit, but I have to admit, I worry far less about them now. The data that I routinely have on my sleep helps me set my own expectations for my day and take control of my sleep. Nothing about my actual sleep has changed, but how I react to it has changed dramatically.

Technology is not the answer to every problem, but I believe that it has the great capability to empower people through information and data. People who have smartphones no longer have to worry about getting lost all the time, and I don't have to worry about my sleep patterns controlling my life.

So thanks, fitbit!

Popular posts from this blog

  • Deep in the dark recesses of Google account settings is one we’d prefer to ignore . It’s one that gives those of us who live our lives online a way to bequeath our digital file cabinet to another. It’s the setting that I recalled -- in a blind panic -- at 4am on this past Halloween. My reaction  @ 4am Rewind The cause for this panic? Well, it started over a year and a half ago in 2013, when I was slotted to attend OSCON. I flew into PDX, excited to attend workshops the next day. I had signed up for a data science with R workshop -- long before I started my flirtation with Julia . While I was unpacking, my back gave out, and I never made it to the workshop. That event kicked off one of the best and worst years of my life (cue the Tale of Two Cities jokes).  My health kept deteriorating, in strange ways. It affected my ability to keep plans with friends, enjoy my life, keep up with day-to-day chores, and eventually my ability to do my job. I remember standing at my des
  • My first job as a software engineer nearly drove me out of the field forever. Many efforts focus on keeping girls and women interested in technology from elementary school through 4-year computer science programs in order to “fill the pipeline” with qualified female engineers. My all-women's education never dissuaded me from pursuing computer science, but that’s the exception to the norm . Education is but a sliver of a woman’s career. However, what happens after those women graduate and get their first job? What happens to those women in the pipeline? As Julie Pagano candidly states : “The pipeline is leaky and full of acid. The pipeline leads to a sewage treatment plant. The pipeline ends in a meat grinder.” I’d like to talk about one such meat grinder. Meat grinder , not for people The environment My first job out of undergrad was as a software engineer at a major company. When I joined, my immediate team was approximately 15-20 people, all of whom were male. Oddly enough,
  • This is the second part of the Julia on Google Compute Engine (GCE) series that I started a few weeks back. The first entry addressed how to set up Julia on a standard GCE instance, and how to run simple scripts. Today, we'll be doing less with Julia , and more with setting things up so you can efficiently write Julia programs and scripts, and make it easy to get the results of your computations. Anatomy of a setup There's the typical disclaimer to be had here, that the optimal setup depends largely upon personal preference and what you're trying to accomplish. My general process is to write locally, validate against small data sets, then run on a high power instance with the output in an arbitrary object store. Your process and setup may vary, but it's likely that you'll want to write access files on your virtual machine, and make your results accessible outside of the machine. The easiest way to do this is to use Google Cloud Storage (GCS) , a highly available a