I was prepared to write a long exposition about how restarting is the hardest thing, about how, after three days off, getting back on track and writing some actual code is next to impossible. It turns out that’s not the hard part, at least not this time.
On Monday Randi and I went to the concert—which was awesome—and we didn’t get home until after midnight. Tuesday I have already written about. By the time I finished the bit of code I was working on, it was after 12:30 when I finally went to sleep. After the baseball game and a rather stressful Wednesday, we finally shuffled in out of the cold at 10:00. Needless to say—but said anyway—I haven’t gotten much sleep this week.
When I sat down to write last night, the code came pouring forth in a torrent which defied my earlier prediction. In fact, I nearly finished the flexible system which will display stats for the player. (Side note: it’s amazing that a system which doesn’t affect actual game play can take so much work; people ought to keep that in mind when they next wonder why a game is taking as long as it is.) By 8:30, though, my consciousness was fading. Fifteen minutes later, I was asleep at my keyboard.
It’s interesting—and timely—that I recently heard a tidbit about how it’s possible to accrue a sort of sleep debt which has to be paid back before normal body function is restored. It’s the science behind why a person sleeps for ten to twelve hours after pulling a few long days. While I understand completely why my body is exhausted, it’s nevertheless annoying.
So here I am at quarter to five Friday morning writing a blog post and working on my code. I’d like to say that this whole experience has taught me a thing or two about my limits and how I need to prioritize, but that would give lie to the fact that I’m awake this early working. My alarm isn’t even supposed to go off for another hour and a half!