Note all the 'that's. That means something like 300 or so pages. Timeline? 2 weeks. Ya know, usually when you're developing something, you a development cycle or two. This thing is going to get kicked out the door (day after tomorrow!) with zero time for debugging, testing, or even for trying to figure out what it is supposed to look like. Oh, and they also have to be able to add pages to this thing, without knowing anything about HTML or the web. Well, I think I've got it covered. But I'm not well known for my bug free code, or flawless mathematically proven program design. (At least not after two weeks. TWO WEEKS! What were the sales people THINKING!?) (Someone's .sig on a mailing list I'm on: "SALES PEOPLE don't hunt elephants but spend time selling elephant they haven't caught, for delivery two days before the season opens.")

Simultaneously, Steve will be taking his leave of this company to go work for Taos. Good ol' Steve. He certainly deserves better than he has got. With Steve and I gone, there will be one person left who can fix the servers if they go down. That's Rick (RiX0r!). He spends a lot of his time on his cell phone, walking around trying to avoid meetings. Meetings, as those who work for large beauracracies know, take up lots more time than they're worth. Communication may be necessary, but the Network Operations crew does(did) a pretty good job without meetings, using IRC to communicate. IRC is actually a decent info exchange tool when you take away the idiots ('anyone know anything about computers?') and horndogs ('r u m or f?').