Archive of February 2008

DC Design Talks Post-Mortem

As I mentioned, today I went to the inaugural DC Design Talks conference in Falls Church, VA. Unfortunately, I ended up staying for just three speakers because:

  1. The conference was even more (pure) design-oriented than I expected
  2. The material covered was more elementary than I had hoped
  3. I had another migraine (my third in three days. argh.)

I mention these things so that it’s very clear what kind of review I can offer and to emphasize that there was more to it than I was around to see.

General Impressions

The conference was held in the pseudo-classroom area of a local web shop. It was small, but that was okay; I also prefer going to concerts in more intimate settings than an arena. I don’t know the numbers and am not good at guessing, but I’d say there were well under a 100 folks in attendance. This was definitely not MacWorld or Adobe MAX, but that’s not necessarily a bad thing. It felt a little less like the first day of high school where you seem to spend half of your day trying to figure out where you’re supposed to be next.

There were a few minor technical glitches, but frankly the venue was small enough that microphones were kind of on the overkill side, anyway. Happily, the organizers seemed to understand their constituency all too well. There were surge protectors and outlets all over the place for the laptops that would surely be out in force at a geek-centric conference. No need to worry about running out of battery life. There was also reliable wi-fi available. It would’ve been nice to have the login credentials printed in the conference literature, but they weren’t hard to track down. That was another huge win. Even the big boys often have trouble providing reliable wi-fi at their events.

The conference was organized a bit like a day of high school. There were nine speakers scheduled (not including the opening remarks) with about a five minute break between each speaker so we were parked in our chairs pretty much the entire time. It would have been nice to have a little more mingling time if for no other reason than to stand up. Perhaps eight sessions would have sufficed. The schedule was packed a little tight.

That brings me to my lone complaint about peripheral matters: the chairs. They were not comfy. My ass was falling asleep within minutes and went completely numb not long after. Knowing I was going to be largely sedentary for the remainder of the day didn’t help matters. If I were to recommend just one item to change, it’d be the chairs. Oy.

Subject Matter

As I mentioned, the subject matter was more design-centric than I expected. I was anticipating a web design conference. That is, a conference covering multiple aspects and disciplines of web design from technologies, to standards, to techniques, to methodologies, etc. The focus, though, was more on pure design as it applies to the web. There’s nothing wrong with that, of course, but as a developer and engineer, I’m the wrong audience. The material just wasn’t varied enough to offer much for me.

Speakers

As I mentioned above – and this can’t be stressed enough – I didn’t stay all day. I stuck around to hear three speakers. I can only speak to the sessions I saw and I won’t generalize beyond that.

Web Typography (Samantha Warren)

My guess is that this was one of Samantha’s first public speaking appearances. She wasn’t polished, but I can get past that pretty easily. I’m not the most polished speaker either. Nonetheless, she was presenting an interesting topic so I was looking forward to hear what she had to say.

Unfortunately, the content didn’t deliver. Her slides were beautiful – she appears to be a very capable designer – but the session didn’t progress much beyond quoting a few definitions of “Typography” and then offering one of her own. There was very little real information, wisdom or experience conveyed. Most of the presentation involved looking at webpage examples and pointing out what I thought were relatively obvious characteristics of the typography chosen. One of the notes I scribbled summed it up pretty well, I think. It said, “Too much what, not enough why or how.”

That said, I did learn a couple of things. I learned about measure and, more importantly, about optimal measure within a document. I also learned that greater leading (line-height in CSS-speak) should be employed on dark backgrounds. I had never thought about that. It would have been nice if she had spent more time discussing why these things were important rather than just telling me that they are important.

Creating a Component Library (Nathan Curtis)

This session essentially covered the organization and reuse of site components – be they wireframe stencils, visual comp elements, code, etc. As an engineer and unabashed fan of reuse and loosely coupled components, this is a topic near and dear. And Nathan was clearly a practiced public speaker. He presented the material very well.

Although the general subject matter and high-level concept are ones that I find compelling and even critical to the long-term success of projects, the specifics of the session didn’t have much to offer me. The material was heavily weighted to the pre-development side of the SDLC. I won’t belabor that point since it’s something I’ve already mentioned.

I did come away thinking, though, that creating this library of “stuff” appeared to be extraordinarily time-consuming and would probably not be a good fit for smaller companies, companies that redesign frequently or companies that, by necessity, must be nimble with their design. The techniques presented seemed best suited for large, static organizations creating large sites. This kind of effort could quickly become cost prohibitive for smaller companies or companies that redesign with any kind of frequency.

Speaking in Styles (Jason Cranford Teague)

This session keyed on another subject I’m fond of – CSS. Jason, too, was a polished speaker and clearly knew his stuff in spite of a minor typo in a bit of Javascript code that some dolt in the peanut gallery just had to point out. There’s one of those at every conference, it seems.

My only issue with this session was that the subject matter wasn’t as substantive as it could have been. Maybe the rest of the audience needed to be sold on why they should be using CSS, but I certainly didn’t. I’ve been evangelizing and espousing the use of CSS for years.

I would have liked to have heard more discussion about how to overcome the limitations of CSS. If the audience needed selling, then this is probably one of the primary reasons selling was required. In my experience, a lot of folks aren’t using CSS as extensively as they should primarily because it’s not an easy thing to do. In addition to the browser limitations (see me looking in your direction, IE?), there are also baked-in language limitations. There’s no way it should be this difficult to create a 100% height container or vertically align one block within another.

As Jason correctly pointed out, the only way to avoid the limitations of CSS is to know and understand those limitations. Too little time was spent highlighting those limitations, much less offering workarounds and alternatives.

Conclusion

On the whole, I think the conference series has real potential. Not for me, maybe, but it’s not the fault of the organizers that I chose to be a developer, right?

Even operating on a shoestring budget, the organizers pulled off an event that, though small, had a professional feel about it. I’d like to see a wider range of material covered and I’d like to see some more advanced topics mixed in with the elementary ones, but this was only the beginning (I hope). I have to believe they’ll evolve down that path as the conference matures.

Being a developer, I’m not sure whether I’ll personally attend on a regular basis, but I suspect I’ll send one of my front-end developers and I’ll definitely be keeping my eye on the schedule in case some developer-oriented material begins to make its way onto the agenda.

The Days Ahead

It looks to be a busy weekend. Tomorrow I get to brave the DC traffic and make my way to the DC Design Talks conference. I’m really looking forward to the conference, but as much as I love DC when I’m actually in DC, I loathe northern Virginia. And even more than I loathe northern Virginia I utterly detest the commute into DC/northern Virginia. If it’s a bad day, it’s not inconceivable that I could end up spending more time in traffic than actually at the conference. Note to self: road rage is not helpful, road rage is not helpful, road rage is not helpful…

Then, on Saturday, I hop a flight to parts unspoken for an unannounced visit only to return the next day. Fly out Saturday morning, return Sunday evening, back to work Monday morning. Looking forward to that. Really.

More Skinning

And thus endeth the latest round of theme updates. This time was working above the comments. The sidebar is gone, with most of its content – at least that which I wanted to keep – having been moved to the header. The header, of course, offers more “stuff” and the logo has been refreshed (hopefully for the better). Additionally post metadata has been moved from the bottom of the post.

As with before, if you see any, um, wonkiness or problems, please let me know by adding a comment to this post.

Tip: Commenting and Uncommenting

Ever wonder why you weren’t the guy (or girl) who invented that thing that’s so simple, stupid and useful that everyone needs one, everyone owns four and the guy (or girl) that actually invented it is a gajillionaire who owns his (or her) own island and has his (or her) own personal armada? You know, something like the beer coozie? Yeah, me too. Anyway, every once in a while, I run across a technical tip that makes me feel that same way. Be with me on this, people; you know where I’m coming from. That tip that’s almost frighteningly obvious and so clearly evident that there’s absolutely no reason in this world that you shouldn’t have thought of it long ago. And, moreover, if you had, you might have added days, weeks or even months to your productive lifespan.

Today, the Ajaxian is offering just such a tip. As stated in the entry, it’s a tip “that make[s] you slap your forehead and say “why didn’t I do that before?”“. Translated from a German post by Dirk Ginader, it’s worth checking out. Wear headgear, though. At the very least, put down that brick your holding before you read it.

1/4/2009: I’ve closed the comments for this post because they seem to be some kind of spammer magnet. Sure, they’ll just move to another post, but I’ve always loved a good game of Whac-a-Mole.

Trying SmartSVN Again

Although I’ve been here before, I decided to give SmartSVN another try. It’s the only one I wasn’t able to actually play with because I wasn’t even able to get it open. This time, though, I put in a little effort.

Instead of just downloading the application and assuming it would, or should, work, I decided to be sure I met the system requirements. The only requirement, as far as I can tell is a JRE of version 1.4.1 or higher.

$java -version java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237) Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)

Requirement met…check. Application downloaded…check. Tarball extracted…check. Application opened…denied (supply your own sound effect, please).

Clearly others use this application. Some, probably, with great success and affection. Why can’t I? The only way I can get it to start is to Show Package Contents and then navigate to Contents > Resources > Java and double click smartsvn.jar. Argh. I can’t believe there’s not a better way.

I’m not even sure that opening the app that way offers full functionality. For example, I can’t find a way to simply connect to a repository and browse its content. I have to create some kind of project first. Even worse, I have to do so by connecting to an existing working directory or by checking out code from one of my existing repositories. At the moment, I want to do neither. I just want to connect and perform a little maintenance directly on the repository.

I guess it’s me and my command line for at least a little longer.

← Earlier Posts Page 1 of 4