shaver

Getting up this morning was really hard. Phil’s wake-up call was right on schedule, but it took me a good 20 minutes after that to gather the will required to actually get out of bed. So tired.

I dropped by the house of the nice man who has my driver’s license, but he was not home. I tried again after dinner, too, and he still wasn’t home. I left a note, hopefully he’ll call.

When I got to work, I read email and code for a bit, and then took a little break to configure vim to my liking. Like the work yesterday with mutt and procmail, this was long-overdue customization. I also installed a build of Mozilla 1.2b with blizzard’s Xft bits turned on, and the web is now very pretty.

Once I was done with that, Andreas and I had a long, and ultimately quite fruitful, conversation about the architecture of our recovery notifications and responses. (“Who do we tell when something goes wrong? What will they do about it? Have you seen my keys?”) I’m glad we had that talk, because I now have a design for this subsystem that does not make me want to scrape my eyes out with fragments of my own skull, but it does mean that I have to write a lot of code this weekend.

In the interests of expediency, and also to reinforce my belief that this redesign was Virtuous and Right, I also wrote a bunch of code today in the current framework. A bit painful, and I felt dirty every time I hacked some piece of code off and copied it somewhere else, but I’m well on my way to passing one of our acceptance tests tomorrow. That’ll be nice, and it’ll give me more test cases against which to validate my rearchitecture work.

I think I’m going to go home early tonight — it’s only 1! — because I want to call first thing tomorrow and find out whose account, exactly, my wire transfer ended up in, because it sure wasn’t mine. Sigh.