Refactoring code is the best. By making a promise to myself to refactor (mercilessly), I can get my code written quickly, It isn’t beautiful, but it works. I get to write lots of code. Then, when it works, I get to go back /and write it again/! Not only that, but I get to make it better. Then, because it’s better, I can use it to do more things, which I code quickly, and then get to re-code.

hit snooze, nine minutes
there is snow, ice, the office
let me stay in bed

old friends are gone now
they don’t answer my email
a cold dry morning

I don’t understand my own modus operandi, but here it is:

1. identify a problem
2. produce simplest easy solution
3. totally ignore solution for X duration
4. get around to trying it

Well, I knew I’d forgotten to tell Number::Tolerant to require 5.6, which it wants. (I like warnings and our, and I’m willing to require 5.6 for them. It’s old!) Now I realize it needs 5.8, too, due to this weird bug:

I really couldn’t stomach the idea of working on the shipping system today, so I opened up the old bug list and looked around. One that caught my eye was a stupid little bug in the CGI form parser for part of our requirements system. It was having trouble turning a field in the form “FLOAT - FLOAT” into a tolerance – with Number::Tolerant, that is.

I’ve been a little depressed, and I’m not sure just why. I haven’t felt very inspired to get anything done, which was OK for relaxing but not great for … well, for getting things done.

On one hand, iTunes crashes all the time when I use it at home. On the other, it is completely awesome for use as an iPod content manager.

I’m happy that I haven’t been distracted by some other object, yet. There are a number of reasons, the most important are probably that I’ve got a real use for Rubric, I’m taking it slow, and there are a few other people who have requests of it.

Thanksgiving was great, despite several attempts by Fate and Me to screw things up.