This is a slide from a talk i'll be giving on Monday.
6 months ago
I often wonder the same :)
Interesting. Is this aimed at the scenario of working with a designer who refuses to adapt to current technology? Or?
For what it's worth, here's one designer who codes what he makes. :)
@Caleb Jacob Aimed at designers who can't code at all, whether or now they have an understanding of what's possible isn't relevant to the talk, but I'm touching on it. :)
I call those people "not real web designers." :)
A more *polite* way of putting it is that you have to know what's possible and what isn't possible before being able to design for it if you want the best experience (and in my opinion, if you actually care about your craft, not just the title and the inflated ego it gives some people).
You can scrape hours, if not days, off of development time and QA if you know what to expect from certain browsers or methodologies and how to compensate for it.
@Mandy McClausky I hear you, but design has always been a collaboration between different craftspeople. It's only in the last decade or so that people expect a "designer" to do everything and then some. Sometimes a little bit of ignorance can produce excellent outcomes -- no matter the headaches induced for the parties involved. If everyone felt the need to learn code before designing for the web then I reckon it would be a far less interesting place. Just my two cents.
@Mike Borsare Definitely not implying people should learn it before they begin (sorry!), just saying that they should have a dedicated interest in understanding it and the progression of the medium.
I always code what I design.....
@Paul Maloney Because you know how to. :) What about those designers who don't know how to code, but feel pressured into it? It'd take years for them to get as good at coding as they are at designing.
I'll do my talk as a blog post. That should give this shot a lot of context.
You should always try code what you've designed. Don't let your lack of coding skill/knowledge hold you back.
@Mandy McClausky I think that's an incredibly limited view of a massive field to be honest. While I do agree it's very helpful that designers should at least be able to prototype and build some of what they/we design, I don't buy that everyone has to be able to do it.
For one, if you're always guided by a safety first, "I know this will work" attitude, you'll be unlikely to produce anything truly innovative. We're seeing it at the moment where so many people are being led by the fact that simple blocks of content will stack up and be responsive etc and that nearly every blog these days is an unimaginative single column of massive text.
Everyone should code what they make. We design interactive experiences, not posters of them.
Thank you, exactly my point.
"For one, if you're always guided by a safety first, "I know this will work" attitude, you'll be unlikely to produce anything truly innovative."
Not to turn this into my own blog post (sorry Paul!), but honestly I think this is exactly the problem with designers that don't code. Their designs are either incredibly simple, boring and not at all stretching the bounds of the platform or they're entirely too complex and their developers don't want to waste their own time learning how to accomplish it and/or bother with the CSS, resulting in a really unfortunate final product that neither the devs nor the designers are happy with but neither can fix. It's also why so many sites these days look exactly the same (insert Bootstrap lulz here).
Furthermore, if you care about designing for the web, you care about keeping up with what's possible and finding the fallbacks you need to implement if you plan on going off the deep end. We are currently relying far too much on non-designers to do the work that designers should be doing and it shows. The web, as a whole, is ugly right now. I would say even more than it was fifteen+ years ago from a visual/UX perspective (given the available tech and ignoring Flash), simply because it was interaction/interface designers working in the industry, not just kids being pushed into it by their guidance counselors or graphic designers who were trying to jump ship.
There's just no reason for people who want to be web designers to be left in the dust when the leap can only further their employability, profitability and (hopefully, therefore) their quality of life. The job market these days already wants/expects these of us, in addition to experience with PHP, Ruby, endless CMSs/eCommerce platforms, and honestly I don't think that's too much to ask. If you want to stay static, there are still plenty of jobs for that.
Edit: I also forgot to add that there are new resources for developers to learn/understand design every day. If other designers aren't snapping up these jobs, developers with design competencies are, and it's always far more important that the product is built over being pretty.
keyboard shortcuts: ← previous shot → next shot L or F like
Show and tell for designers
What are you working on? Dribbble is a community of designers sharing screenshots of their work, process, and projects.
Copyright © 2009–2013 Dribbble LLC. All screenshots © their respective owners. Shipped from Salem, Mass. USA.
Follow Dribbble on Twitter