Here we are. The clock on my computer says we have exactly a week to go, and the scary thing is, I think we're more ready than we've been in years past. Jeff brought the Ops server up last night, and I started testing it to make sure the basic functions were ready to go.

I've found a few oddities, and it's not fully functional yet, but I've got a list of fixes and tweaks, and everything looks manageable.

I have to brag a little. I was quiet, so Jeff could make the announcement over on his site first, but Jeff is now a part of the Huntsville Master Chorale.

Hard to believe it's that time of year already. I've had my head in other things for almost a year now, and it shows. From reading the boards, I'm one of the last people to get into "con mode." Everyone else on tech seems to be frothing at the bit to get back to work, and me, I'm a bit hesitant.

So here I am, testing again. I wasn't happy with the last attempt I made at turning an entry private, so I'm going to try this new version out. This latest version is a password-protection on a node-by-node basis. Problem is, I can't test it without posting, and that's going to spray tests around everywhere.

Specifically, I need to know how the node looks if you don't have the password, and I want to know how it acts in an RSS feed.

So let's see what happens....

*posts*

I'm unwilling to explain more at this time, but:

Just because something's right doesn't make it easy.

That's all.

Dear friends: it's on. We have a candidate for tweet of the week. This tweet is an example of what happens when you introduce someone to barbecue, send him home to a land where it's not easily obtained, and then taunt him via twitter that you're about to have some of the tasty stuff:

@hsvlocals I CAN HAS BBQ? YOU MAILS. I EATS.

My work here is clearly done.

(I am 'domesticat' on twitter. I have my tweets set to 'protected,' which means you have to request access, but that's easy to do.)