After Dominic Canterbury and Rachel Whalley's excellent blogging event Monday night, a few folks headed off to Liberty for some brew, foodstuff, and talk.
Sitting off to the side of Dan McComb and Stuart Updegrave, sipping a brew and slowly losing the feeling in my cheeks, I found myself utterly lost in a sea of adjectives I had never before associated with the ever-evolving world of web development. The beer helped me make it through this, I swear. I found myself insidiously scribbling little phrases on an ATM receipt behind my beer glass. The beer made me tell Dan and Stuart what I was writing, and I told them that I just had to post about it. To my surprise, they gave their blessings. They were drinking too.
Now, I have been designing websites for eight years, and I have a blast doing it. Designing websites engages several of my design geek tendencies all at once. I get to totally geek out on a healthy dose of project management and strategic planning, indulge in my questionably healthy habit of scrutinizing other sites in finite detail during the research phase, pry out the perfectionist in me for outlining the information architecture and standards, apply my love of typography, and write good content for clients who wrote their own copy twenty-six years ago and have never, ever changed it, spelling errors and all. Then there is the design and layout phase. When I started in advertising, a double-truck ad spread was a dream project, so huge was the canvas. Not in my wildest dreams did I ever imagine that I might have a five, fifty, or one-hundred page canvas to strategically design. After all that geeking, I get to once again invoke my perfectionist tendencies, making my web developer pull his hair out in large clumps as I say, "Please move that graphic one pixel to the right." Or two to the left. Next, there is the testing and tweaking phase, wherein we all get to wax poetically in unison about the latest a**hole tax that Microsoft ought to be charged for not being able to make Internet Explorer even remotely standards compliant. Lastly, the launch and relative euphoria of completing a project that makes the client excited, more prosperous, and happy to write a check.
Talking about code is an entirely different melancholy beast. When clients began expecting designers to learn how to code in the late 90's, my interest in web design briefly waned, but I quickly adopted the stance that coding was best left to programmers. It was one of the best business decisions I have ever made. (Coincidentally, it is right in step with the Biznik way.) For every site I have done since, I have teamed with a developer during the planning, development, and testing stages, and the approach has paid off in spades. I am able to collaborate, learn, share, provide my clients with a hand-picked team that suits their unique needs, and I am much happier.
So, there I was sitting betwixt Dan and Stuart, coders extraordinaire, my imagination still giddy with excitement about the blogging event, eyeballs swirling in opposite directions, listening to the two of them talk about code. 'Where did Dominic go?,' I found my inner dialogue asking. He was four tables away, being 'The Dude,' or just talking with a friend.
I heard a tale about twenty lines of amazing code that did something or other. Dan showed the depth of the lines of code with both hands. Stuart was amazed. I listened to tidbits about the second coming of the Biznik site with new features and ease of use. 'How could it be any easier,' I wondered silently. Dan verbally marched on about more code. And then more code. And still, more code. My beer disappeared at an ever-increasing speed as the now completely foreign language, or code, conversation became a cloudy background noise thing. My chimera might have understood. All of a sudden, I heard Stuart passionately exclaim, "That is some sexy code!" I looked to my left and saw his eyes wide, a smile ripped across his face, eyebrows raised, forehead slightly wrinkled. Women have gotten lesser frenzied looks from straight, horny men. I looked to my right to see Dan with a similar intensity and expression, eyebrows peaked, forehead crumpled. The two of them leaned in to the conversation just a slight bit. I rifled through my wallet, looking for an elusive piece of paper, something, anything to jot a note about 'sexy code.'
Next, I heard them talking about Ruby. I had heard of Ruby before. Ruby is code that was named after the precious gemstone, making it more appealing to developers than HTML, or PHP, or .net, but that's not what Dan and Stuart were talking about. As I studied the wall, I heard the adjective 'sleek,' and then I knew I had to write about this. Dan asked if the conversation was boring me to tears. "No," I said, "This is, uhh, well..." Just then Dominic returned to the table, and I didn't have to answer.
I am glad that there are people who can get excited about code. I need these people. The world needs them. Heck, what's not to get excited about. We have code that sexy, Ruby, even sleek. What's next? Scarlet? Wilhelmina? Oooh, Cuddly?