• just realized I didn’t say happy birthday to my wife!!!!!!! oh shit. #
• return to work prep. expense report. vacation tracking. health fsa paperwork for q1. all while the dogs glare at me for not yet walking them #
• @jernst thanks man looking forward to it. #

Ooooh — Tasty!, originally uploaded by ReidCarlberg.

Mmmmm….. Old Chili Sauce. I probably bought it before moving to this house in 2003, which means I bothered to move it from the condo. I wonder if I moved it to the condo from the apartment a couple of years before.

I have no idea. Anything is possible when you’re dealing with chili sauce that expired in 2005.

I’ve been on vacation for a while, but am trying to catch up on some misc paperwork today before heading back on Monday.   Part of that is updating my vacation days to reflect when The Critter was actually born and the days I took off.  Unfortunately, there seems to be an issue with the calendar data picker.  You select a day and it simple comes back to the same day you were already on.  I’ve tried this on Win32 FF & IE 6 as well as on OSX FF and Safari.  Same thing.  Weird.

Regarding software bugs and how to write code:

The No. 1 predictor—I doubt this will surprise anyone—is the amount of code in a given module. The more code, the greater the odds of a bug. This seems kind of obvious: If all code has bugs, the more code in a module the more likely it will have bugs. However, as unremarkable as this correlation is, it testifies powerfully to the benefit of small, discrete methods, which is a keystone of object-oriented programming.

This from “Debugging Cyclomatic Complexity” over at SD Times.  I occasionally get feedback in re: my preference for small methods and small objects, so I always like stumbling across things like this.

And about that cyclomatic complexity — this article argues that it’s near useless as a predictor of software defects.  On the bright side, it still sounds really cool.