Comments on: 5 Good Reasons Why Designers Should Code

By: Crys

Crys — Tue, 17 Aug 2010 15:40:40 +0000

Well, I know this is a few months old, but I’m just seeing it today. I wanted to comment on the architect analogy. If you can draw technical schematics and can mathematically determine the thickness of glass you have to use for an interior non-load-bearing wall to still be physically sound, you’re an architect. This is the technical side of building design and these are the people who are equally comfortable outputting highly technical and sometimes esoteric prototypes and schematics (ie: functional wireframes and html/css prototypes that are programmer-ready) and outputting the creative elevation drawings of all sides of the building (the static photoshop mockup).

If you are able to creatively decorate a space for human use but are not capable of creating functional schematics, you are not an architect. You are an interior designer. This can be a demanding job and does require a certain amount of talent and creativity, but don’t try to call yourself an architect. Anyone with a good eye for color and form can be an interior designer. Only people who have a good eye for color and form AND also an understanding on a technical level of the properties of materials as well as how people will use the space and flow from one room to another get to call themselves architects.

By: Barbara

Barbara — Thu, 01 Jul 2010 12:05:49 +0000

Very interesting post. I agree with you on every point. As a beginner in a web design agency, I often feel frustrated not to know enough about coding. That’s why I’m going to learn it.
I think as you do that both coding and designing are linked. The more you know coding and designing at the same time, the more you push your creativity further.

By: jaro

jaro — Fri, 02 Apr 2010 02:42:35 +0000

number one reason, you don’t have to pay someone to code it for you!

By: Jeff S.

Jeff S. — Mon, 22 Mar 2010 13:42:36 +0000

What are some good resources for someone to jump right into (x)HTML/CSS and make them a part of their package?

By: David Lewis

David Lewis — Thu, 11 Mar 2010 00:13:28 +0000

p.s. I chose the name “union” for my freelance business specifically because of the idea that I do both design and code. My personal site needs a total redo (it’s just a simple resume+portfolio from years ago… in table layout no less)… but when I do redo it… the copy will talk about the idea of union… about the idea of treating things in a holistic and strategic way… about the merging of disciplines such that you can’t separate one from the other. I think web design is the ultimate “design-build” business.

Sorry. Am I getting a little “out there”? LOL.

By: David Lewis

David Lewis — Thu, 11 Mar 2010 00:06:10 +0000

Right on. I feel the same way. I think of myself not as an artist or a designer… but as an artisan. I can’t imagine doing a great design but never having the satisfaction of actually building it! My whole would would never be anything more than pixels in Photoshop. Dead. To bring your creation to life… that’s HUGE. I love both aspects equally. I love the design process and I love the coding. I love all of it. I can’t imagine giving up one half of the equation. I’m even doing some of my own PHP coding now too… creating simple WordPress plugins and such. The more I can do myself, the more satisfaction I get from the job.

By: David Lewis

David Lewis — Wed, 10 Mar 2010 23:59:39 +0000

I taught myself graphic design starting in the early 90′s and then started building websites in 1994. So I’ve always done both. Back then, bad web design was REALLY bad. Like, horrendously bad. When the background attribute first came out (not to be confused with CSS backgrounds)… it seemed like the entire web (it was small at the time) turned into a tie-dyed t-shirt overnight. Being both a designer and in interface developer gave me the skills to create really great websites in a sea of breathtaking mediocrity. These days you can accomplish almost anything with CSS… so it’s not AS critical to know both… but it still has to be an advantage. Back in the days of font tags, table layout, td backgrounds and pixel wedges… you almost HAD to know code in order to create a good design. If you didn’t know HTML you’d end up designing all kinds of things that simple could not be built. But it’s still an advantage. If you have no idea about code, you can’t really grasp the concepts of type on the web, font resizing, background tiling and positioning… etc.

By: Rick

Rick — Sat, 06 Mar 2010 01:50:18 +0000

Interesting post / thread. I am a back-end programmer and have been for many years.

Very topical reading this as I have recently had an interview with a (well established) ad / communications agency wishing to bring their digital requirements in house. The thing that struck me was they seem to be expecting whoever goes into the role to cover all aspects of the build. I just don’t think this is a reasonable expectation anymore, if it ever was.

Sure, I *can* code xhtml / css from a psd or whatever; but (as you point out) a psd / graphic when translated to code by anyone but the designer maybe not what was in the designers minds eye and it’s almost certainly going to deviate. Anyone Designing for the web *needs* and absolutely *must* have a thorough understanding of the ‘environmental’ constraints of the browser too, and I think that only comes from writing client side code (akin to print designers understanding ‘the fold’). I would even extend that to also cover a thorough understanding of accessibility issues / techniques.

At the end of the day, for me it’s this: If you want to provide a quality service to your clients then these boundaries must be defined. I simply find it a little naive that anyone would think otherwise – gone, thankfully, are the days of the ‘webmaster’. My job is to ensure all the back-end interactions are handled in a secure and robust manner; the designers is to ensure all the front end aspects are taken care of. Two highly skilled disciplines in their own right.

Now, I have been asked back for a second interview to speak with the creative guys. How do I get this across in a subtle not in-your-face way without alienating myself (the position does actually sound really nice)???

By: mauco

mauco — Wed, 03 Mar 2010 06:00:27 +0000

I like the way you summarized the whole issue in your point #1 “The combination of a designing in Photoshop (or whatever software you use) along with HTML & CSS is greater than the sum of their parts.” Its best for a designer to know a bit about coding and vice versa.

By: Lauren

Lauren — Tue, 02 Mar 2010 19:19:54 +0000

For those suggesting that designers should not let awareness of the limitations of HTML/CSS box in their creativity, and should instead design as innovation and challenge those ‘lazy’ developers (and I know I am grossly oversimplifying), let’s not lose sight of scope. Often times developers are pushing back in the context of a schedule and a budget, not just for the sake of moaning about effort. Sure, with enough time and trial-and-error a lot of things *can* be done, but that doesn’t mean it’s what the developer signed up for when they gave the project manager their initial estimates on which the contract was based.

This is especially true when the designs are going to be handed off to a completely different agency to implement. Food for thought!