First off, a disclaimer: I never have and never will consider myself a technical developer. After having the pleasure of knowing and working alongside a number of talented developers — many of whom I also consider some of the most creative thinkers I’ve ever met — I recognize that my kung-fu is nothing in comparison. And thankfully in my role on the account management side of the agencies at which I’ve worked, no one has had to rely on my coding skills to get the job done.

That said, however, I’m constantly amazed by how many folks that profess a career expertise in interactive development, digital marketing or social media arenas don’t bother to stretch into this territory.  So, loyal reader(s), is a brief versioned history of Patchchord and my personal attempts at better understanding what happens under the hood of a web site.

v1.0/2.0 - Contrary to what you see here, I’ve actually been blogging since about 2002 in one form or another. I developed my first site using some cheap server space via Netfirms and leveraging a now-defunct blogging platform called Greymatter. The site was frame-based (I guess I missed the memo from usability guru Jakob Nielsen six years prior when I was in college working on that music performance degree) and the capper was that rather than purchasing a vanity URL, I instead used a go.to address. This was my very first intro into HTML. As I recall, a re-skinning of the site was the only difference between v1.0 and v2.0.  Mercifully, none of my original v1.0 site graphic files have survived (*cough* *cough*).

v3.0 - Somewhere around 2004, I unleashed the next iteration of my site, the first to carry the patchchord.com URL.  I had wised up and gotten rid of the frames and ditched Greymatter.  Originally using Movable Type, I eventually opted instead for Textpattern, though around this time I started my first freelance forays into web design for friends and family using MT as the more layman-friendly content management system.  Here I added CSS and some MySQL basics to my bag of tricks. Say goodbye to Netfirms and hello to Dreamhost.

v4.0 - 2005 saw the re-purposing of patchchord.com into what would become a two-year experiment in grassroots journalism on the local KC music scene.  For more of that story you can always click here, but to take a look at the site itself, a proper archive version still exists.  Two years of constant work on the site exposed me to a ton more about CSS, simple javascripting, SEO, podcasting, PHP, writing to MySQL databases and assorted other oddments and necessities.

v4.5 - Sometime during this public foray with patchchord.com, I’d say late 2006 or so, I realized how much I missed having a personal web space.  As a result, I bought leftcoastmissourian.com and launched a new blog using a push-button install of WordPress. This was about the time I started to mess around with extending beyond a personal blog to incorporate other features, like mobile Flickr integration and other social media tools, by discovering the joys of WordPress plug-ins.

v5.0 - After the previous patchchord.com shut down, the domain remained idle for about a year before I repurposed it back to being a personal space last winter and re-launched with this current iteration, closing down leftcoastmissourian.com at the same time.  This time around, it’s been all about social media integration and understanding how my personal space on the web should integrate with all the other assorted places I like to hang out.

So why the detailed change log?  I firmly believe that if you’re going to work in this space, you should at least be able to hang with code on some basic levels.  How else are you going to have any sort of valuable insight into how this magical thing we call the web is put together?  

Web hosting, software platforms, development timeframes, integration — if you can speak to these things with more of a “sleeves up” understanding of how it all works, you have a more credible voice in front of a client.  Similarly, you will also have a much better idea of the right questions you should be asking your internal team on any given project.

No one should expect an account management-type to be able to code the next Facebook or keep pace with the giants over at Google Labs.  But if you’re going to talk the talk, then why not try walking the walk for a change?