So the hilarious hiring hijinks are over, happily. We hired the guy I wanted to hire, he starts in two weeks, and we're all anticipating delivering all of our IT problems into his hands at about 9:15 that morning. ;) If he doesn't have a nervous breakdown by about 12, he should be okay.

On the other hand, we may be hiring for two more positions, one of which I would actually have to be involved with, so the whole mad process could be starting up again. On the positive side, hiring some more help would mean I had more time to spend on the uber-cool parts of my job.

I've been getting more interested in Wikis lately. I mean, I'd heard about them before, and had used the Portland Pattern Repository a fair bit, but hadn't had the chance to really investigate before. (For one thing, wikis seemed a bit unstructured for Boeing's environment. ;) At my current job, though, there are huge masses of domain knowledge just floating about, and a Wiki seems like a good way to start fixing that knowledge and making it accessible.

The only problem is that, of the relatively few Wikis designed to run in our (heavily Windows-centric) environment, none were really friendly or intuitive. So, like any good little software engineer, I'm writing my own. :) Oh, sure, I tell myself that it's a great opportunity to learn ASP.Net, practice some design patterns in VB.Net, and end up with a valuable tool for my work life, but the honest truth is that those are just icing on the cake. I like to code, and I don't have the patience to dig through someone else's code and fix what [I think] is wrong with it, so... :)