So, new site for work going up tonight -- everyone's a bit punchy. There's a problem with moving usernames and passwords over from the old site -- because about 400 people have passwords that are too long to fit into the new system.

"How long?" we asked.
"28 characters long," we were told.

Um, what the fuck? Did someone hit our site after a three-day crystal meth bender and type in the lyrics to "Sabbath, Bloody Sabbath?"

What would *your* obnoxiously long password be? Comment away.

So, gang, in case anyone had any doubts whatsoever, I'm putting this out publically: if anything ever happens to me where I'm in a "vegetative state?" YANK THE TUBES. Let me go. I would not want to be kept alive that way.

Got it?

Yes, yes, radio silence, blah blah blah. Sorry about that. We're getting ready to launch a new design of our Web site at work -- with an updated back-end content tool, and...a second, totally new, back-end content tool. Why two? Because one is doing most of our static content, and it's great for that. With this iteration, it's better than ever. The other is doing more dynamic, customized stuff -- commerce, event management, galas, donations -- and that's great for that type of information. (Hey, some projects require both a hammer and a drill!)

The only catch is getting the two to play together. So: no sleep 'till launch!

1.5 weeks to go. Aieeee!

Fellow Web designers, take note -- I've coined a term. Stonehenged: to take an extremely large image, shrink it down to 200 pixels, and have to display it on your site -- no matter that you can't actually read the copy on the image, and have no idea what it may be or mean. In other words: when you need a really big image, but have to make do with a really small one. Adapted from "This is Spinal Tap." Dwarves not included.