Asymptomatic

Seething Designer Rant

Many designers (and the people that hire them) don't realize or appreciate what happens on the development side of their web projects. Tweaking things a pixel this way or that for them is a matter of dragging it around in Photoshop until it looks good. They then hand it off to a developer expecting it's done, when in reality we not only need to do the same thing they did (at least in terms of positioning, if not aesthetics), but we have to do it by typing in code that they're typically completely incapable of producing themselves. Regardless of having to reproduce their designs in code, we frequently need at least rudimentary skills with design tools like Photoshop both to open their files and prepare their designs for the web, and the overlap is such that the only things we're really missing are 4 years of design classes (trivial compared to what we're forced by our profession to learn almost daily), and that harder to obtain ineffable sense of what "looks good".

In addition to converting their designs to code, we often need to produce, install, or at least troubleshoot a back end that lets someone create content, make it account in some way for the fact that those content creators are going to screw up the designer's pixel-perfect vision for the site with poorly-formed content, and code it all so that it scales over hundreds of pages that individually vary the one or two designs they've so elegantly produced. And too often, we're left to explain issues to the client of why the site doesn't do anything interactive (because there's no design for it), or why their navigation colors won't appear on top of the image that the client swaps in later (because it doesn't magically change from low-contrast black to high-contrast white), or why search engines will never find that paragraph of text that absolutely must be in that bizzaro font in that weird texture pattern in front of that stock art I've seen lately on your competitor's site.

Continues here →

I recognize that I do not have a designer's design skill. Nonetheless, what I do is not only a completely congruent skill set - in my estimation, requiring more than just the designer-like natural ability to be creative and persistent competence, but also real, continuous learning and refinement of technology and technique - but it is also an art in that it takes creativity to solve all of the problems that these graphic designers carelessly cast to us to solve without a clue themselves for how to do it, or even in most cases that it's a problem at all.

Yes, it's work, and it takes time, and it's every bit as complex as as design, and takes just as much creativity. Just because you can't see it or understand it doesn't mean you should not appreciate it; doesn't mean it is not so. I'll never be belittled by a designer again. My accumulation of years of experience applied to turning your pretty pictures into a working, breathing web site demands your respect, and I'll have it.

And to any designer that says "that's not me", sure. You're right. That's not you. But if you're saying, "I don't see what's so hard," then you're the one with the problem. But you're not reading my site anyway, are you?

Other Posts

Comments

  1. Jen Simmons

    Yeah. I hear you. And I've met a few designers like who you've describe. But in my opinion, any designer who only uses Photoshop (or Illustrator, or the like) to draw flat pictures of webpages, but doesn't know HTML, CSS, or anything about how web technology works — in my opinion, those people are unqualified to design websites and really don't know what they are doing.

    The web is not print. Web "pages" are complex technological breathing things — not flat pieces of paper. Besides, to be a decent print designer, you better understand what is going to happen to your design on the press, or you will get messy blobs of ink everywhere. You have to know technology to design.

    These "designers" are usually young ones, fresh out of art school who had professors who also know nothing about how the technology actually works... these designers need to learn more, and learn how to teach themselves. Especially before they start getting uppity and belittling developers. They put those of us designers who do know what we are doing to shame.

    My father had the same frustration his whole professional life. He was a carpenter who became a draftsman who became an architect, back in the day when being an architect didn't require a college degree, let alone a masters degree. He later was the boss of many baby architects, fresh out of grad school, who though the world of construction was all about art school theory. He told stories over and over, of how these kids thought they know so much, and yet didn't know how to draw a bathroom; how he had to teach them everything from square one. It drove him nuts.

    Shame on the schools and huge web agencies who create arrogant, overly-specialized, unqualified "designers". It's only recently that some can get into the field of designing for the web, and have no idea how the web works.

    As Jeffrey Zeldman recently said "real web designers write code. Always have, always will." http://twitter.com/zeldman/statuses/4818978868

  2. Joseph LeBlanc

    I was going to write this rant, but you did a much better job than I ever could have.

    Don't know about your work situation. However, I do not own a copy of PhotoShop. When someone asks me to turn their PSD into a webpage, I tell them that they will be responsible for finding someone that can do this for them. I can help with some limited HTML/CSS debugging, but draw the line there.

    It's 2009: if you're a designer who doesn't know HTML/CSS, you have no business doing web design.

  3. Equally frustrating is designers who *think* they know HTML/CSS, and deliver table-infested, Dreamweaver-generated CSS nightmares. At that point, I'd rather wrestle with Photoshop.

  4. Mr. Designer

    That was a great post. I'm an interactive designer. I design Web pages/applications in Photoshop and Illustrator. I also do the HTML/CSS.

    I started out as a Web designer in 2000, with a 4 year degree in graphic design. I was always trying to make my Web pages perfect and consistent across browsers. I gave that challenge up a few years ago. I now design my Web pages to have flexibility. Many parts of the layouts can shift a pixel or two in different browsers. I don't expect text to wrap perfectly. I don't create designs that consist of nothing but sliced images that have to be put together like puzzle pieces. I make designs that have "floaty" pieces, that can shift, and be modular. I try to use HTML/CSS to generate the interface as much as I can w/o relying on images.

    Is my design process slightly less creative? Yes. Is my design process better for updates, cross browser display, SEO, Web accessibility, and less time consuming? Yes.

    Graphic designers everywhere just need to relax and shouldn't be such control freaks. If they truly want to understand how Web design works, they need to at least learn HTML and CSS. They need to work under someone with Web design experience. Then they'll understand the challenges Web designers face.

  5. Noel Wiggins

    I agree with the statements that a website designer should be aware of all aspects of "design" just making something look pretty isn't good enough one has to know how these designs are limited once launched on different browsers and operating systems, in addition to business issues like SEO.

    The burden of a well designed website should not rest on the shoulders of the programmers only, the designer needs to be apart of the entire process, and if anything should learn some of the pho and css skills needed to help smooth the process...

    --

    Thanks and Regards

    Noel for Nopun.com

swindler-cave
Real Time Web Analytics