Web Design: Are You A Designer or a Programmer?
by Adrian Hanft, (25 comments)
I doubt that anyone noticed that Be A Design Group’s code is now valid HTML. Although the site doesn’t work any differently, and everything looks exactly the same, I feel like this was a real accomplishment. I don’t know about you, but the web design I do is nothing like the web design I learned in school. When I started out, web design was just a matter of slicing up large Photoshop images. Now the sites I work on rely so heavily on coding that sometimes I wonder if this is even design. Almost everything I know about building a website I have learned on my own by trial and error. As I have grown into the role of web designer, things like validation, usability and stylesheets have become increasingly important to me. Whether I like it or not, I have turned into something I never would have thought possible: a programmer. At least that is what it seems like. Troubleshooting HTML sure doesn’t feel like graphic design. I doubt that there are many graphic designers that got into web design because of the appeal of learning HTML. Maybe all websites should be designed in Photoshop, and then a programmer should be hired to build the code. We are designers, not programmers, right? Wrong. Like it or not, a good web designer is going to have to be a good programmer, too. Disagree? Drop me some comments…

Comments (25)
ctipton said:
Adrian- I agree completely. Our role as designers is to use our talents to promote a client’s message/brand to the desired audience. If a website looks great but can only be properly viewed in Safari we’ve failed. In some cases we may have programmers to do the coding for us, but even in those instances the more we know about what they do, the better our chances of getting the results we want.
Like any design medium, the better you know the technologies behind the medium (web:coding, advertising:printing, architecture:construction, broadcast:editing, etc.) the better you’re able to execute your design. Of course sometimes we fall into the trap of not being able to see beyond a technology and it ends up dictating our design: “I will use 12 frames on my website because I can! And DreameWeaver makes it easy!”
Posted on December 4, 2005
p.berkbigler said:
Programming aptitude will only continue to grow as a foundational skill for any designers hoping to crack open web design with any sort of seriousness - there will certainly be plenty of designers who find successful collaborations with individuals who are even bigger code gurus and create the visuals for the “mechanics” the programmer is providing.
It’s already a bit staggering to examine what the basic toolbox of a web designer needs to be: HTML, CSS, XHTML, ASP, JScript, etc. and that’s simply scratching the surface. I’d add to that: motivated learner, not easily frustrated by repetitive work, highly detail oriented, exploratory / analytical, and ready to bang their head against code for hours trying to find minute errors.
All of this is still somewhat the beginnings of an even bigger side effect of web development: web design education and its eventual alumni. As the faculty I work with continue to discuss the realities of offering web / multimedia / interactive courses at our school (the next “big thing” in education along the lines of the boom in the late 80’s / early 90’s when schools decided to bring digital design / art into their programs), it’s clear that general programming knowledge / understanding is going to be necessary at the foundations level and then build from there.
Your comment about feeling more like a programmer than a designer when you debug code seems simply like a necessary growing pain - I’m sure there will also come a time when new media designers will simply talk about code issues like print designers toss around kerning issues and bitmapping concerns. It was only so long ago that typographers handled all of the type issues and designers were more concerned with overall page layout along with directing the photography (maybe).
The world keeps turning and our desktop continues to fill up with technologies that put numerous abilities at our fingertips…It only seems we’re running out of fingertips to operate those technologies with!
I guess the bigger hope is that something like the phrase “He / she codes like a designer” will also quickly become a rich compliment rather than a slam in the near future…
Posted on December 4, 2005
Nate said:
One thing I think needs to be made clear is the difference between markup and code. Since X/HTML is just a means of presenting the info and I don’t think it’s fair to call ourselves programmers if our role is limited to arguing with a CSS for hours on-end (harrowing as it may be). However, if we’re building PHP and JavaScript applications in addition - then we can justifiably do so.
That said, the term ‘web designer’ seems to have a such a loose definition: there are some who are strictly graphic designers, some really excellent hybrid designers/coders and there are programmers who know their way around Adobe CS.
My old boss, a professor at Cal State Long Beach, said it would be impossible to feature a web design curriculum since the topic was too broad and the definition too nebulous. If designers wanted they could take programming courses and if programmers wanted, they could take design courses - and this would get them far enough.
Any thoughts on this?
Posted on December 5, 2005
Michael Dogan said:
Adrian, my story is identical in every way. What I want to put out there is how come a web developer; which I usually refer to, quite rightly, as a “Code Monkey” can earn north of $50, 60, even 70k or more while us lowely Graphic Designers are often expected to do what they can do for much much less.
Yes, yes, we are no dbase developers, but oddly enough, I’ve already been asked to do this. And before that, I clearly remember being offered a contract, that, at the time seemed so easy — until I walked into the meeting with the client on monday morning. The entire site was CSS and div tags. At the end, the Project Manager turns to me and says “…If you think you can do it, that is…”
Oh well. I don’t complain about work. But interesting stories will always be there.
At least this new age is one for the digital pen, agreed all?
Posted on December 5, 2005
Jolo said:
I agree, absolutely. The commonness of two different position has become “ONE” from a graphic designer’s view point. Nowadays, with the competitive market/environment we have, designers must realize that even though not required, learning to program (especially “web standards”) is a must to stay put and inline within the context of communicating your content, be it design-wise or programming-wise.
But regardless of that, the word programmer or likewise the “programer-wise” notion should not be a hindrance in terms of our role as designers (web designer), our priority still is to communicate not the sole program itself.
Posted on December 5, 2005
Drew Davies said:
Adrian,
You baited us, so you got it: I disagree. To say “…a good web designer is going to have to be a good programmer, too” is like suggesting that a good print designer has to be a virtuoso on a Heidelberg 6-color press.
Certainly, a designer becomes a more well-rounded communicator the more they know about the processes which translate their ideas into reality. But our firm designs for a wide variety of media, and we are not highly-trained pressmen, web coders, sign fabricators, or toy manufacturers. To be valuable, we need to focus our energies on creatively solving the problem at hand, and letting trained professionals translate our solution into reality. At least at Oxide we focus on our strengths — strategic design and visual communication — and let best-of-breed partners handle the commodity end of things.
Posted on December 5, 2005
Douglas d'Aquino said:
I completely agree with you. As a web designer, i believe that coding (or markup) is as important as design. You can’t do the markup without knowing the objectives of the design and you can’t do design without knowing how this would looks like when became ready.
I don’t know much of Java, for example, but my job as webdesigner is to put that code in my design somehow… that’s not coding, but is hard too. And because we need to integer this data, we must study these languages. As the time pass by, we became more and more like an Hybrid them coders or designers
Posted on December 5, 2005
Christopher Gee said:
Great topic. You all raise some interesting points. Since the beginning of the web, I’ve heard print graphic designers whine and complain about understing web programming technology turning them into programmers.
Understanding how to do some coding and markup if one does interaction design is akin to understanding pre-press and print production if one does print.
When I first started my career in the late 80’s, I started out in print. I quickly learned as a junior designer that if I wanted to be able to produce great print work, regardless of how beautiful my comps were, I was going to have to learn about pre-press and printing techniques. Without a good knowledge of pre-press and printing techniques, I would consistently see my beautiful comps result in disappointing printed pieces.
During the mid-90’s, when I decided to pursue interaction design, I quickly learned that if was going to produce great interactive work, I was going to have to learn about programming and web technology. Without that knowledge, I’d forever be dependent on programmers — who do not have design sensibilities — to take on my own responsibilities in designing the interactive experience of the user.
The same way that poor pre-press/printing knowledge would result in disappointing printed pieces, poor knowledge of programming/web technologies would result in disappointing interactive experiences.
Chris Gee
Posted on December 5, 2005
Bennett said:
The coding that many of you do is not designing. You may be a designer, and your knowledge may inform your design decisions, but when you are working with code, you become a programmer. I’m not saying that this is a bad thing, I just don’t think we should confuse the two disciplines. When I’m prepping a file for the printer, my designing is done. I then put on the production hat. Finding a person that designs 100% of the time is rare. Working with code and designing take two different parts of the brain. Some designers have the ability to do both very well, but they are not one-in-the-same.
I’m not sure all of my “clarifying” is important or not, but I thought I would throw it out there.
Posted on December 5, 2005
Christopher Gee said:
Coding is different from programming just as pre-press is different from operating a printing press. When I did print, I was required to know something of print techniques and technology. What I knew amounted to less than a fraction of what the printing press operators knew.
Similarly, my wife is a programmer. She can write entire applications from the ground up. The coding I can do which can bring minor effects or affect the style of a page/site is a tiny fraction of what she knows as a programmer.
Like any kind of design one may do, you MUST know the medium and the technology used in it in order to do an effective job.
Chris Gee
Posted on December 5, 2005
Nate said:
Again, I think the best way to put it is by making the distinction between markup and programming. XHTML and CSS have nothing to do with logic: it uses no operators, functions nor variables and so it’s markup, not code. Therefore it’s not programming.
I think saying so cheapens what our code-geek counterparts have to struggle through on a daily basis.
Posted on December 5, 2005
Nate said:
I should correct myself in saying that XHTML has nothing to do with logic. Being ‘Strict HTML’ of course implies that it must follow a certain syntax/structure, but still this is nothing in comparison to writing an application from the ground up.
Posted on December 5, 2005
Kyle said:
Good topic; I was just discussing this with a web designer Friday.
Along the same lines as the previous posts, I know enough technical stuff about my OS and print design apps that I can fix most issues that arise. However, if I’m busy—or stumped—I call in the IT experts to fix it for me.
The “creative-in-a-different-way” side of design that can be called technical/programming/production/scientific pops up in many ways: fixing desktop printing issues (hardware and software), software conflicts, color management, writing scripts to save you time, and even simple things like knowing how to use FTP sites/don’t use spaces in FTP folders for maximum compatibility.
Designers adept at both sides are better off (less reliable on others) and increase their marketability.
Posted on December 5, 2005
Paul Ducco said:
I’m a designer, I used to create my own code until I realised not only was I frustrating myself, I was not helping ANYONE move forward in terms of development. I outsource programming now, and honestly I think it makes for a more creative environemnt (collaboration) and the outcome is better sites/applications developed properly which hit the mark creatively as well.
IThat being said, I do like to stay in touch with some knowledge of code etc, so when managing an interactive project I am able to understand what the designer/programmers are on about, rather than them getting pissed off with a project manager/art director who just stares dumbfounded at them when talking “tech”
Posted on December 5, 2005
Randy said:
I don’t necessarily agree that being a good web designer means being a good programmer. Many places that do a lot of web design are now hiring programmers as well as designers. But I do think that a good web designer should be up to speed with what coding can and cannot do on the web. When I was in school they began offering a web design and programming minor. It was both computer science students and graphic designers. We all had to take both design courses and programming courses. The designers were tested heavily on design and only on basic concepts of coding. The computer science students were tested heavily on code and only the basics of design. I think the school had the right approach…designers should understand what is going on with the code on their site and know its limitations, and programmers should understand the concepts of design to understand why the designer placed things where he did. In a perfect world we would find people that are excellent at both, but you’ll rarely find that now. I think someday in the future we will see kids coming out of school who are proficient at both, as they will realize that if they can do both then they are worth more to an employer.
Posted on December 5, 2005
kadavy said:
Congratulations, Adrian, on getting the site to validate! I know how tough it can be, but the site, and the web for that matter, are better for it.
I’m pleased to see so many people in agreement with you. I had given up on discussing this issue with print designers, as it seems only those who truly understand web programming are convinced of its value. Those who don’t don’t even know what they don’t know, and it’s difficult to explain this to them - since they don’t know! Are there any designers who have learned web programming yet later deemed that knowledge unhelpful? I think I hear claws scraping along the walls of the pit of obsolescence.
Programming the presentation of a site (XHTML, CSS, JavaScript) is absolutely design, because you must understand the strengths and limitations of your medium to create your vision on the web just as you would have to understand the strengths and limitations or oil, acrylic, or watercolor, or spot vs. process color.
There are blurred areas of web design where it is a point of diminishing returns to know. While I have learned some PHP, and hope to learn more database stuff and more JavaScript, those technologies are really icing on the cake that help me get by on small projects when I don’t have an engineer available to me. There are realms that the engineers I work with have an expertise in that really require knowledge of the fundamentals of computer science, and would be a waste for me to get too far into (heavy Java, database optimization, web security, and server hardware).
Posted on December 6, 2005
dcasey said:
I used to be a Software Engineer at EVIL-LARGE-COMPANY-X. We used to laugh at Web masters that called themselves programmers… any high school student can do that. Java != JavaScript
Recently, I have left my world of engineering and am working towards a Graphic Design degree. I have built a few Web sites and cannot believe how frustrating it can be, even with a programming background. The standards issue is a huge deterrant. Web programming has come a long way in the past few years, but it has a ways to go to be as robust and easy to program as a “real” language. PHP and CSS are leaps forward.
Web programming is just another facet of design. Some people will get into it and others will not. I don’t think that designers have to know how to program Web pages, although a familiarization would be good for a reality check. It just depends on what you are interested in doing. Some designers will want to hire a specialist for the heavier coding.
People are going to call themselves what they want. Some are self-proclaimed Graphic Designers. Web design can be programming, but it is certainly not on the same level as a Software Engineer writing code in Java, C or C++. And, not all Graphic Designers are going to know or should know how to code a site.
Posted on December 6, 2005
professional web design said:
interesting….i enjoyed reading your comments. as for my share, i dont know but when i started learning in a computer school (my major is multimedia and web design) so basically they taught us both how to program and design in the web. either way,i think a designer can also be a good programmer depends also on their interst, it doesnt matter anyway as long you do what you can do and your happy baout it
Posted on December 6, 2005
Nate Voss said:
I spent the better part of a year delving into HTML coding. I can tell you one thing: it’s not like riding a bike. Once you learn this stuff, you really need to use it or lose it.
What was interesting was, once I was neck deep in a few projects, deemed “super-simple HTML sites” by my design firm (we, like others, outsourced our more complicated web projects), I really got a chance to see life from the other side of the coin and it gave a me a huge appreciation for the knowledge and ingenuity of a learned Programmer versus someone like me, a Designer who moonlights as a programmer.
Innane comments like “I don’t like the way the bullet points look on a Mac in Explorer on Jon Doe’s PC over there” and “why can’t all the text just be a Gif or Jpeg?” were enough to put me over the edge. At one point I swore they wanted a rainbow to leap out of the screen and land in the user’s lap. The fact of the matter was, they needed a programmer. Even for what, admittedly, began as a “simple” site, their needs as freaking designers to have control over every single detail at all times in all applications quickly took the project out of the realm of my expertise.
That’s my big roundabout way of saying that specialization is A Okay in my book. But if your solid programmer is also a solid designer, it seems like you could have your cake and eat it, too.
Posted on December 6, 2005
Nate (Luzod) said:
I like the rainbow/lap remark. I’m going to have to use that one…
Fortunately 99% of my clients use iExplore on WinXP. Unfortunately it’s the most difficult thing to work with, since I do all my development on FireFox with Mac.
For any of you stuck in the trenches of XHTML validation, there’s a great FireFox extension that will check your pages for you without having to bring up the W3 site each time.
http://users.skynet.be/mgueury/mozilla/
Posted on December 6, 2005
Dariusz Janczewski said:
Have anyone noticed that we are discussing a distinction between two SEPARATE professions by definition?
Even a static web site should be considered a MULTIMEDIA project. Using a feature film media as an example, there are very few movie directors who, in addition to directing, are also responsible for photography, fashion design, or editing, or… score. Sure, Spielberg knows his lenses, and supposedly even has a large soundtrack collection. But, I do believe he does not meddle in John Williams territory by correcting the composer’s score notes…
Ideally, a web site should be produced by collaboration of at least a graphic designer, copy writer, and a …programmer. If it is not, it simply is not what it could be. To use a film analogy again, it becomes an Indie. Aren’t we wasting time discussing this issue because we feel guilty of doing more of what we should not and not enough of that what we should (design)? However, we all have very good excuses, don’t we? Including yours truly, I am afraid.
Posted on December 23, 2005
Bennett said:
Dariusz, Why can’t we have both “Indie” style designers and “Hollywood” style designers? I think both are valid models, and work well for different people. I think it all depends on your personality type.
There are also those directors in the Hollywood arena that do more than just direct. For instance, sometimes Robert Rodriguez writes, directs, edits (in Avid) and scores the movie. He feels comfortable in all of these arenas, so why should he be constrained by the title of “Director”?
What about those designers that print their own work? Should Aesthetic Apparatus stop doing their own printing, because it is not design.
Definitions and titles can be important, as long as they don’t constrain us.
Posted on December 23, 2005
Penn Aragon said:
As the web is the “new media”… I think designers should be familiar with it as we are with the rest of our tools (type, paint, photography, etc.)… How far we go with this tool– is up to the designer. Not everyone is a typographer… not everyone is a web-ographer? But we should have at least a pretty good grasp on the medium. Merry XML-mas!
Posted on December 23, 2005
Christopher Gee said:
Sure, Spielberg knows his lenses, and supposedly even has a large soundtrack collection. But, I do believe he does not meddle in John Williams territory by correcting the composer’s score notes…
But I’ll bet Spielberg gets to edit his own movies — a rare luxury amongst Hollywood directors.
It’s something most directors fight for because they realize that to allow the studio to have the final cut of the film means they are giving over their creative vision to those who do not have the same creative sensibilities.
It’s the same with interaction design, really. I think that programmers absolutely should be used but not to do the work that lazy, designers with a curiosity deficit should be doing. Programmers — just like any other professionals — should be brought in to do the things a designer can not. To bring things to a project that a designer never could.
Call me crazy but I think the designer should rule the style sheet/layout and define the site’s overall interactivity. Naturally we bring in photographers, programmers, writers, etc. but just like with the movie director analogy, each of those professionals must do their job in concert with MY vision as the designer.
I pull the strings. Steven Spielberg will not tell John Williams what key he should play in or how to conduct but he will certainly tell him his vision for the mood of a scene and have Williams compose and re-compose until Williams’ music conforms to Spielberg’s vision.
The better Spielberg understands music and how it can build tension or manipulate emotion, the more successfully integrated Williams’ music will be with his dramatic visions.
Does this mean Spielberg should become a musician? No. Does this mean Spielberg would be as successful a director if he simply “handed over” his film to John Williams and said “you take care of that music composing stuff?” NO WAY!
It’s no accident that Spielberg has made some of the most effective use of music to build emotion and tension that film has ever seen. “Jaws” and “Raiders of the Lost Ark” come immediately to mind.
It’s the same with designers who design for the web. The more designers think their job has ended once they put together a neat Photoshop layout, the less effective their design solutions will be — whether their work is eventually produced for print or web.
The interactive designer has to understand how each of the various interactive elements will fit into their overall vision. If they don’t have an overall vision, they need to get one rather than push their responsibilities onto non-designer contractors.
.chris{}
Posted on December 27, 2005
mukesh marwah said:
Hi as a designer i say me is graphic designer but me to htmlisation and i love to do this work as its better to do code urself as designer u can mould up the things and understand things in good way……so whether its a programming or designing what matter….work should be code and clean as html is also an art of design and sense of understanding hope u are agree
Posted on August 9, 2007