So that was a thing

Hello! We’re on a new server now!

We’re also on a new host!

And since we got hacked on the old host, we’re on a fresh WordPress install!

Every day is a new adventure.

Things I have done in the last three weeks

Hectic, harrowing, and headachey are the ways to describe the last three weeks, but so much of it is design-oriented I felt like it was time for a blog post.

  • I attended Future Insights Live in Las Vegas and live-tweeted the conference sessions I attended. (In short: this is a great conference you should attend, despite it being in Las Vegas. Yes, I said “despite”. I’m a shy introvert who’s allergic to cigarette smoke and that place was a new circle of hell for me.) 
  • I built a new website called BorrowABlog.com. What’s that about? Well occasionally folks say they wish they had a blog to post to, but they only really have one or two things they occasionally want to write about. If that describes you, register, blog when you want, and link to your blog post from wherever.
  • I built a website for close friends who lost their son to brain cancer, and are now raising money for cancer research. (I’d love to link to it, but the parents in question haven’t given it the thumbs-up yet.)
  • I accepted a new position at work, moving from Interaction Designer back to Information Architect — with a lot of interaction design still in my future. I’m really excited to join my new team and stretch a bit more into the “UX generalist” role. It’s a little scary, too (what new job isn’t?) because I’ll be moving to a different division of the company and serving a different business group for the first time in thirteen years.
  • I wrote two articles — like actual articles, not just tech writing — for aforementioned primary employer, which at some point will be published up on the main site. As an Engish major with heavy IT leanings (or a Software Engineer Poet, depending on the day) I’m really grateful to have the opportunity to communicate in words as well as designs.

In other words, life is full of change, but those changes are good.

The Zoo Story philosophy, and when it doesn’t work.

In his play The Zoo Story, Edward Albee once wrote, “Sometimes a person has to go a very long distance out of his way to come back a short distance correctly.”

I’ve always seen that as a bit of a motto for my design work. As designers, it’s rare that we get handed a problem to solve that has a straightforward easy-to-implement solution. It’s all about the context of the problem, especially when we’re creating the context as we go. A thoroughly researched and implemented design requires capability strategy, iteration, research, iteration, design, iteration, testing, iteration, iteration, and iteration. You can try to cut off somewhere in the middle or skip a few steps, but you’ll usually come out of it with something that feels just a bit like you installed shelves with only some of the pieces that were supposed to be in the box. There’s nothing wrong with approaching complex problems with the mindset that the journey will be long, but the destination might be two blocks over from where you started.

Today, though, I’m thinking of rethinking the Zoo Story approach to this blog.

I’ve been going a long distance out of my way to design and develop a visually-attractive responsive theme for this blog, so I could come back the short distance of “provide evidence that you can produce a quality blog” correctly. I want to prove to myself that I could work on mobile-first content-first responsive design projects by making this a responsive-design (responsively-designed?) blog about design, development, and user experience.

I’ve hand-coded the theme(s) to my other blog since I moved to WordPress in 2004, and before that I hand-coded all the pages. I learned most of my CSS and all of my PHP developing for my now-sleeping comic. When I started, there was no good canned theme solution for comic presentation in WordPress. (There still isn’t. That’s a rant for another day and one that requires responsive images to be solved.)

The problems I ran into were threefold:

First, WordPress’s crack development team beat me to it. Their 2011 theme is already responsive. So to make my! very! own! responsive design theme, I had to cover my eyes and LALALALA a lot to pretend I hadn’t seen anything in their code. Even though it’s excellent, and it works for my site structure.

Second, the development of a responsive design layout takes a lot of work. It is an absolutely great experience from an educational standpoint, and one I plan to continue. It’s just not something I can produce fast enough to also blog on a regular basis, which was the point of having a blog.

Third, I’ve had a stubborn blind spot about using other peoples’ code for my website(s) since the beginning. I was “raised” in the world of apps producing truly crap code “for me” (see Microsoft Word, FrontPage, and even Dreamweaver to a certain extent). I struggle against using any code-generation system because my gut says it must be full of bloat. Why use WordPress’s image uploader when a simple <img src> declaration would be enough to meet my needs?

But the fact is that, for a responsive site with responsive images, they’ve got a damn good system going here.

It might be worth noting that in The Zoo Story the “right” solution involves forcing an unsuspecting stranger to knife you. So, y’know, there’s an argument to be made for staying local and not provoking others into violence.

Sometimes, you have to go a long way out of your way to come back a short distance correctly. But sometimes, sometimes you can walk two blocks and reach the same destination, without any fuss or heartache at all.

Hello world!

It’s obligatory to use that as the name of your first post, same as it is to use it for the first application you write in a new language.

At least, that’s what these fellas behind me with the suits, dark glasses, and baseball bats contend. 

Let’s go with that.