Web Designers who can’t code anything?
Over the past few weeks there have been riots in blogland, which all kicked off from this tweet by Elliot Jay Stocks.
Elliot said:
Honestly, I’m shocked that in 2010 I’m still coming across ‘web designers’ who can’t code their own designs. No excuse.
To further clarify and explain what he had meant by the tweet, Elliot published a blog article to fully explain his views. Blog riots followed, and countless designers and developers published their own blog articles both attacking, and supporting what Elliot said.
One of the reasons I like having a blog is because it lets me share my opinion on topics that affect me. That’s why I’m writing this.
Elliot did retract what he said (to an extent), and said something like “okay, designers do not have to be able to code, but they need to be aware of it”. I think he may have got lynched if he didn’t come out with some sort of statement like that, in all honesty. There are some hardcore Designers out there, you know.
Mark Boulton said in his response article he that generally he felt Designers didn’t need to know how to code, but needed to at least be aware of what it does. Fair point.
But, there is one major issue that stood out for me that was not really touched on. How employable are Web Designers that cannot build a basic website?
I am a Designer that designs for Web and Print (Web & Graphic Designer), and have learned to code XHTML & CSS quite well. Being able to code the interface you design is empowering, and will give you a great deal of satisfaction from your work.
There are brilliant User Interface Designers out there that probably cannot code a single line of CSS, and still deliver awesome work, which then is built by a Developer. And I understand that, and salute them for being brilliant at what they do.
However, my point is this - if you are a young Web Designer starting out, and you cannot code any of your own designs into a basic working website, then you will really limit your options for employment.
It is easy for Designers at the top end of the industry to say that Web Designers don’t need to know how to code, when they do know how to code. I wouldn’t say that to any young Web Designer that’s just starting out. With a bit of time, and effort, it is possible to learn XHTML and CSS to at least a basic/intermediate level, and doing that will make life easier when going to job interviews.
In harsh economic times employers are wanting more bang for their buck, and are expecting candidates to be able to do more stuff. I’m not saying it’s fair, because it isn’t, but that is the how it is – especially in Northern Ireland where I’m from.
I’m saying that every Web Designer should learn how to code their designs, then at least have the option to choose not to on down the line, and take a step back, and let the Developers do their thing. Having a more in depth understanding of how a website is built will make the designer much better at what they do, and open up more doors for employment.
Do you agree with me?
Related articles:
- Misconceptions about Web Designers
- Do you really need a degree to work as a Designer?
- Firerift… a completely new breed of CMS
- Web Inspired Typographic Poster Designs
- My Favourite Design Blogs
Yup I think the general consensus by almost everyone, is that they should at least know the basics of coding, but that they don’t have to actually code. I’m glad they don’t too, otherwise I’d be out of business
My experience is that if you’re looking for full-time employment from a company, you probably have to know XHTML/CSS, but if you’re working as a freelancer, it’s not as necessary. Most of my freelance clients hire me strictly for the design, because they already have their own development teams.
In many circumstances, such as working in a large agency, it makes perfect sense that a web designer wouldn’t need to code a single html tag or scrap of CSS.
But, ideally, what got that designer that job in the first place was being a REALLY GOOD web designer. And in order to be really good, the designer needs to understand the capabilities and limitations of HTML and CSS, how a design is cut up for HTML, potential problems and browser compatibility pitfalls, etc. And in order to know enough of this stuff to be a really good web designer, I think it’s imperative for the designer to have spent time coding.
Otherwise, design decisions are going to end up being made by the developer, as the design is refit and massaged into something for the web. And, just as the designer has no need to be *as good* of a coder as the developer, the reverse is true too. The result: the designer’s not happy because the final look of the site isn’t as good as their original, the developer’s not happy because they’ve spent a lot of extra working “fixing” the design, and the client’s not happy because the final look of the site isn’t a perfect match with the design they approved. Everyone loses.
@Amber – you do seem to have crafted out a good little niche there with the stuff you do, and from what I have seen you aren’t a bad Designer either.
@Daniel – I agree with you to an extent. If you are marketing yourself as a “User Interface Designer” then absolutely you may get employed by agencies to do visual work for them. But if you are dealing with the average Joe client on the street they may be more likely to want you to make them a live website. It really depends on the clients you are marketing yourself towards.
@David – I totally agree with you. I work for a small agency and I’m expected to do quite a few different things, which is good, and keeps me on my toes. Typically, I would design the website, then code the front-end, and then pass it over to our Developer who would build in something like WordPress. I can code WordPress though (not a master, but I can do it), but my job role is a creative one, and I am far happier letting the more skilled programmer do the work they are better at doing. I’m more in “the zone” working on designs, and visual stuff.
My experience is right the opposite of Daniel
Working as a freelancer, clients expect me to do everything, from design to front-end development (XHTML, CSSm jQuery), to back-end development (PHP, MySQL) as well!
If I were employed in a company I probably would have to do only a small part of a project, being a couple of web designers we have to do everything (and we have to know at least the basis of anything).
Thanks for the post, always useful to discuss these points.
When people approach me looking for work done Freelance, that would be my experience too, Federica. I find that those clients expect us to be able to do everything!
The more you know… the more useful you are to any client, and any employer.
It’s the fact that there are some “Web Designers” out there that don’t even want to know more – that’s the part I don’t get. Even when I wasn’t great at coding I wanted to know more, and learned it. And I’m still learning new stuff every month – that’s how it should be!
P.S. Thanks for the comments guys!
I learned how to code because I felt it necessary. How else does a solo designer to break away from the limitations of print (budgets/distance/etc.) w/o knowing how to code? I didn’t come to web armed with a dev department in my back pocket.
Turns out I really like CSS, especially CSS3!
When I’m working in Photoshop, I’m thinking ahead to the code and how I’ll implement effects. Conversely, when I’m coding, I make design improvements along the way. The two parts are intertwined.
It seems that ultimately, the work environment affects the need (or not) for designer to code. Still, knowledge never hurts!
Another really good point there, Catherine! It would be quite hard to break away totally independent without knowing how to code.
I’m probably quite odd in that I actually don’t like Photoshop (we’ll save that for another blog post though). I love illustrator for drawing, logos and some interface designs. But I would mostly enjoy using Fireworks for UI design. Fireworks is a bit like the unwanted brother of Photoshop, but I love it! Photoshop just scares me!
*stay tuned for more on that last one
I thought web design=someone with the ability to code. Web and coding go hand in hand. Print designers need to know how to produce a final working print product, why wouldn’t web designers have to produce a final working web product.
Great article, Mark! I’m a little torn on this one because I have friends who are front-end designers and they are not required to, nor expected to code. Ever.
But, I learned to code because I felt (and still feel) that we are moving toward a place where designers are expected to be one-stop-shops. But, I don’t think that wanting a designer to be a jack-of-all-trades really gives clients the best result.
In MY opinion, in an ideal world. Front-end designers would ONLY design, and back-end designers would ONLY code. Why? Because it’s so much easier to be good at your job if you can concentrate on the one aspect that you are best at.
BUT, I also feel that front-end designers need to have a working knowledge of code and what can or can’t be done. AND, I think that programmers need to have some sense of design. As designers, we catch a lot of flack for not knowing how to code — but have you ever worked with a programmer with no sense of design? They don’t pick out the details in the design. They don’t pay attention to alignment issues or proportion. It really works both ways.
I’m lucky because as I started to learn HTML and CSS, I found that I love it. I find it relaxing to sit and code. But, for those with tremendous visual design skills that may not take as well to coding, I don’t see any reason they can’t be successful designers.
I absolutely think, that to be a “web designer” you ought to at least know some basic XHTML and CSS. I bet most of the people jumping up and down are those who don’t know how, and deep down in the back of their minds know that the should really know the basics at least.
I do understand where you are coming from, Manda. But I think anyone that floats under the job title of Web Designer should at least have a general understanding of the code. They don’t necessarily always have to code their own work, but they should at least having a desire to want to learn about the mechanics that make the websites work. For me… this is what separates Graphic Designers from Web Designers.
I totally agree too about the Web Developers needing to have some understanding of design to at least pick up on the little details put in there. But at the same time, I think that could be expecting something that may never be possible from someone who’s mind doesn’t work like a Designers.
It is quite a complex topic for me too in some ways because… I am NOT natural programmer or coder, whatsoever. It is a forced effort for me to learn this stuff, but I have made myself learn what I needed to in order to bring some of my work to life.
All the best Web Designers I know are awesome coders and designers, so with that being the benchmark for what success is… I think in some ways that does illustrate the need to know the code.
I totally agree that the term “web designer” indicates that you can both design and code. I also agree that all people designing ANYTHING for the web should have some working knowledge of code — or at least what can and can’t be done online.
But I also think that it makes a lot of sense to have “front-end designers” and “back-end developers” because no matter how much I learn about HTML and CSS, there is no way that I’ll be able to keep up with PHP, SQL, and jQuery while ALSO maintaining my design skills. It’s just too much for one person to do really well (in most cases).
I’m with you — I code (and I actually enjoy it). I learned because I felt the same way you do: it’s the gold standard. But, it’s frustrating that we all accept that “Programmers minds don’t work that way — they just can’t do design” but as an artist, my mind is supposed to be able to handle anything. Most designers aren’t mathematically inclined, and code is frustrating for them. For those designers, I think it’s important that they learn what can or can’t be achieved in webdesign with code — but I don’t necessarily think that they need to be able to pull out wordpad and code everything from scratch to be successful. Would they be MORE successful if they could code AND design? Probably. But, I don’t think that all designers who can’t code should pack it up and find a new career.
ps. Loving this discussion
Great topic!
I think if a Designer is established, and gets plenty of work designing interfaces, then that’s fantastic, and they should keep going.
But… for any young Designer starting out that wants to be a Web Designer, it is going to be a LOT harder to get a job in the current economy without being able to do all of the things expected of a full-pledged Web Designer. That would be the main thing I want to emphacise… so much is getting expected now by employers. I have even heard of some employers in Belfast here asking for Web Designers to have experience with “Web Technologies”, i.e. things like jQuery and AJAX.
It’s a tough industry out there to break into now, and the harsh economic times are making it harder to get that ideal job (because employers want more and more from candidates). We don’t make the rules unfortunately, so we just have to roll with the times now and again.
I’ve nothing to add to this convo except my avatar.
Nice read, I also read the article Elliot Jay Stocks wrote a while back. I must say I agree with his point of view but I do understand why people don’t want to code.
You stated that not being able to code “will really limit your options for employment”, I don’t totally agree with you on this one. In smaller companies it’s a valid point but I think that for larger companies it’s no problem at all. The larger the companies like to have employers who are more specialized because they have well.. more employers.
Personally I don’t like to code and therefor I don’t do it that much but, I’m capable of doing so on a basic level.
But you see… if you can’t be considered for the smaller companies, then you will indeed limit your options to only the larger companies.
I think that it’s fair enough to not be a coder if you’re a Graphic Designer, but if you’re operating under the title of Web Designer, then I do think there needs to be some level of understanding there – for me, that’s how I would separate the roles.
Yes your wright, there is a difference between Graphic Designers and Web Designers. Web Designers should have some level of understanding how to code a website indeed. So I must say I agree with your point.
Good article, it’s a topic that’s currently racking my brain,
I work for a company who associate “development” as part of the design department. There is no “development team”, just a Design team.
My company recently merged and I had to take a mini interview to keep my job.
I’m a web designer, My primary skill is design, I also code in HTML and CSS to W3C standards.
I took the test, and the interviewer who knew nothing about code, asked if I had intermediate knowledge of Javascript. I told him no, but I know how to implement Jquery…
Although I kept my job, apparently I didn’t at first, because of my reply being “no” to Javascript Knowledge.
My Company hire designers for under 30k to come up with fresh concept designs and code the final product in HTML/CSS Flash & Jquery. It’s extremely taxing, and slows down the workflow, but my team are used to it, and to be honest they allow themselves to be walked over.
Before I merged, my old company had a web developer who would do the coding. I can code to the same level as him, but for better workflow, it makes sense that i solely work on creating a design that will bring in revenue, pass it on.., then work on the next design.
to conclude my rant..
I agree that Web designers in a company should know how to code in HTML/CSS. But only to know the techniques and limitations of HTML/CSS.
btw Mark, I agree Fireworks is the better solution for UI. I absolutely hate photoshop. Unfortunately, my new design team don’t use fireworks. So I “must” use photoshop. say’s my new Head of design.