Designer, Developer or Both?

In looking at job postings across the web, I see quite a few jobs titled “Web Designer” listing PHP/MySQL/.NET, etc. as requirements. My skills are heavy in the use of Adobe Suite, XHTML, CSS, JavaScript and SEO and I think of myself as a Web Designer/Frontend Developer. I dabble in some of the “backend” development so I can speak intelligently to developers, but as a designer, I prefer to focus on the tools/skills that enable me to create good design.

So my question is; Are companies/HR people truly looking for a designer with these skills or are they confused as to what difference there is between a designer and a developer?

Designing before content is complete

It’s been a while since I posted, but I’m in the throes of a project and this is a great time to write about this topic.

It’s almost always impossible, but if you can, try to get your client to provide all final content before you start designing. If you’ve been in design a while you know this is a struggle, but an important one. If you’re newer get ready for a constant battle.

Here’s how it goes: Client contacts you and needs a new website/brochure/mailer. You say “Sure!”, excited by the prospect of new work. You set up the exploratory meeting to flush out ideas and at this meeting you ask what content will be involved. The client usually says something like “well, we want (these pages) and on each page we will need some words about each topic and we’d like some pictures as well”. You ask if they have the copy and pictures ready and they typically (99% of the time) respond with “well, we thought you could go ahead and start designing with some placeholder pictures and words until we have everything”.

I usually try to explain to my clients that the challenge in this approach is that a change in the number of images or the amount of copy can quickly alter the layout/balance of the design and if it’s a print piece, change the final size of the document. Not to mention it can quickly blow any deadline set if they are constantly changing content. If they insist on starting design first, you can either decline the project, or, if you need the income, pad your bid to compensate for the never ending changes that are sure to come (of course remember not to charge for the padded time you don’t use).

There are more ways to deal with this situation. What do you do?

Clean, Well Documented Code

So, this post isn’t so much for the UI as it is for the CI (coder interface).

Over the years we have seen quite a growth in the capabilities of the Internet. With this growth has come many new languages (programming code) and tools. I have had the opportunity to work in several teams utilizing most of these different languages. The one constant has been the need of clean, well written and properly documented code.

Let me break it down a bit:
Clean, well written code – This is pretty obvious. As a front end developer (sometimes you are the designer as well) you will likely be working with back end developers at some point. It is integral to the timing and understanding of the project to ensure that your code is as clean as possible. I typically try to include HTML and CSS comments in any area that I feel will clarify anything I have done. I have worked with plenty of programmers that don’t know much HTML/CSS and they have always appreciated this.

Documentation – This is more for a programmer than a designer. Best practice is to document any original code and how it is used. In Object Oriented Programming (OOP) you can use this documentation to outline your functions, arrays, etc. This document will be invaluable should you have to hand your project off to another programmer at some point. This can apply to a designer, who should use this same type of documentation to outline the formatting of their page, their Javascript details, etc.

Sure, this adds to the workload and there are times that you just want to sit at your desk, throw in the earphones and code. But, it’s an important step to the success of every project, especially the more people involved and/if a future modification should happen. Plus, it’s billable.

Flash

I’ve been approached several times with potential clients wanting a complete site built in Flash. While I understand the “wow” factor that can come with it, Flash should not be used for complete sites most of the time. The problem I see more than anything is load times. Users want to get to the content of your site NOW, making them wait can greatly increase the chance that they will leave before your site can completely load.

To me it is the equivalent of having shoppers stand outside your store while they watch you finish eating lunch on the other side of locked glass doors. They are there, money in hand, so let them in! There are other issues such as SEO, accessibility, etc., but we’ll talk about those another time.

So, when should one use Flash? Here are my suggestions on when to and when not to:

Good for Flash – Sites that are heavily related to the entertainment industry (movies, TV, music), for example. My reasoning behind this is that users are expecting this type of experience, so are more willing to wait.

Bad for Flash – Basically any other site such as brochure, information and eCommerce sites.

Flash is still great for delivering rich media content such as videos, games and for interactive ads. So my suggestion is a blend of “static” content enhanced with rich media whenever possible.

Why good web design is important

When I first started in the web business (’96) you had roughly 30 seconds to gain your visitor’s attention. Today, you have about 3 seconds. The main reasons this has changed is because access speeds have increase tremendously (anyone else remember 14.4k dial up?) and because the competition for traffic has increased even more tremendously.

Your goal should be to make the biggest impact possible in the shortest amount of time. You have to ensure your brand, content, and message are easy to understand. Once you have their eyes, you have to keep them on your site if you want to sell your goods, convey your message and so on. The surest way to make this happen is through good design.

Professional Web Designers understand how good design should enhance, not overtake, your content. They understand how navigation works, how people use it and how to design with good navigation in mind. They know how to use design to make your message stand out, make your products more enticing. This will greatly increase the likelihood that your visitors will become customers.

Yes, your nephew just took a high school class in computers and can “probably” build your site for next to nothing. But, what you save in the short run could cost you a great deal more in the long run if your visitors don’t understand your site or flat don’t like it. You have 3 seconds to gain visitors/customers or they WILL go to your competitor. Don’t let the savings of a few dollars upfront cost you many dollars in the long run.

The start of something blog.

Hello all.

I decided to start sharing my thoughts on design through this magical “Blog” thing. While I have been involved with most forms of design (Print, Video, Web), I will focus mostly on Web as this is where I have spent most of my time (over 14 years).

As non web projects come up and I feel like I can share something of value, I’ll post those as well.

I welcome all feedback, so please comment, etc. as you wish.

Rus