Over Christmas I was flicking around the internet one evening and stumbled across a blog post here, and after reading it, it got me thinking about events that have happened in my life that leads me to believe that Elliot’s tweet was absolutely correct.
Honestly, I'm shocked that in 2010 I'm still coming across 'web designers' who can't code their own designs. No excuse.
— Elliot Jay Stocks (@elliotjaystocks) February 17, 2010
(an old Tweet I know but still just as relevant I think)
If someone is calling themselves a “web designer” they should not only be able to design but have the ability to visually or physically be able to work through the build process for a project’s visual aspect. Thus knowing and getting to know the limitations some designs may have before the final design is signed off by the client, making them think thats what there getting. I can’t remember how many times I have been sent a flat Photoshop (psd) file that is both complex and near impossible to build with the time allocated and the clients budget. Where the designer can’t code and therefore has no reference for the technical abilities needed to achieve the finished design and look they are after.
Web Designers – Can’t or Won’t
As in Elliot’s post there is a clear line between designers who can’t code and those who won’t code. However I think this is somewhat miss leaving in his post as he refers to “can’t” as ‘choosing not to’ – so they can but choose not too – where as I think there are designers who can’t because they don’t know how and need to be taught but are willing to learn.
What’s the options?
So the question is, should people who are web designers be able to code what they see visually? Or maybe we should be designing in the browser from the word go, after all it is 2013 (nearly 2014). Leaving photoshop for what it was built for?
I would love to hear your views from both designers and developers below.
Photo by takorii