Categories / Trends

Should Designers Code?

Daniel Schwarz Last updated: April 10, 2024 · 5 min read

It’s 2016, not 2006. Roles like User Interface Designer and Front-End Developer are more favorable than the old-school Web Designer, and they have been for a while now. We’ve become much more attuned to the different stages of building a website, not to mention the fact that there are more technologies, more trends and more competing websites than ever before.

Every aspect of a website needs a specialized type of designer.

And when Google changes its algorithm to accommodate a change in the way we design for screens (like they did with mobile-friendliness/responsive design), you know it’s a huge deal.

But how can you be sure that the component you’re designing (whether you’re using Photoshop or Sketch) is responsive if you don’t code? It sort of makes you wonder, did we make a mistake by splitting “web design†into multiple specialized fields? Or did we do ourselves a favor by focusing our efforts?

Let’s debate it out.

Why Designers Should Code

In bigger teams, somebody else has the role of developer. Developers have to take your design, represent it with words and make it functional. While you may have an idea (whether you visually conceptualize it or not) how the website should adapt to different screen sizes, and how the website should react to a user’s interaction, a developer has to actually make it happen.

Forming creative ideas without boundaries is a wonderful thing to be able to do, but sadly technology does have boundaries – by disregarding the limitations of what code can actually accomplish, you risk creating bumps further down the road.

Performance and Code Maintenance

Performance and code maintenance are two things a web developer has to think about, however, one of the underlying factors that contribute to bloated code and slow websites is the complexity of the design, which the developer may have no involvement in.

Perceived loading times, actual loading times and code complexity are three boundaries that would be better considered before handing a visual design over to a web developer.

Designing With Code

If you tend to build smaller websites then the benefits of being code-savvy are quite obvious. It doesn’t take much work to design and code smaller websites – in fact it makes it a whole lot easier to design with code, directly in the browser.

Many designers enjoy working this way because it eliminates the need for forward-thinking in regards to writing code that runs fast and looks clean. If another developer is taking care of the code, then you run the risk of them either implementing heavy workarounds to fit your visual concept, or them sending you back to the drawing board to come up with a more practical layout.

Why Designers Shouldn’t Code

Designing and coding? Well, that’s a lot of work. Although many of us may be capable of such a feat, it’s a strain on the brain. You’d be responsible for so many things: visual aesthetics, user experiences, interaction design, search engine optimization, branding, mobile-friendliness, code maintenance and so on. Teaming up with a developer sure has its advantages.

Focusing Your Efforts

Having a team (or simply a buddy to work with) means that more energy can be channeled into the design while somebody else holds the fort elsewhere. Having less responsibility means having a clearer mind and efforts that are more focused.

You Shouldn’t Code If You Simply Don’t Like It

Some designers don’t even like programming, and I’m a firm believer of doing only what you love. If you’re doing something that you’re not passionate about you’ll never be awesome at it.

Conclusion: The Sweet Spot?

In my opinion, the necessity to know how to code is circumstantial. What enables you to code (as well as design) efficiently depends on your personality. Do you enjoy reiterating over several rough ideas at once (i.e. being a creative), or are you more neurotic (i.e. you obsess over the final details)?

If you chose “final detailsâ€, then you’re likely the gal/guy who takes all of the ideas and designs something solid with it. When you’re done, you hand it to the developer, right? Personally, I believe designers should be able to defend the viability of their work and offer a “this should be code-able†guarantee.

But that doesn’t necessarily mean that web designers should code, or even know how to code to a so-called “developer standardâ€, however, an understanding of the fundamentals could be a huge step towards a workflow with fewer bumps in the road.

What’s your take?

Equally, web developers could explore a deeper understanding of user experiences and the importance of detail. So, should designers code, or not? Or is communication, regardless of skillset, the real secret to an outstanding designer-developer team?

Let’s discuss!

Daniel Schwarz is a full-time design writer and digital nomad. He’s the founder of Airwalk Studios, a company that recently switched their interests from freelance design to content creation. Now they’re working on writing books and magazines for design enthusiasts. Daniel is 25 years of age, originally from London.

Products Seen In This Post:

getpaidtowrite-banner

Lettering Worksheets
Getting started with hand lettering?
Free lettering worksheets

Download these worksheets and start practicing with simple instructions and tracing exercises.

Download now!
Tags:
About the Author
Author
Daniel Schwarz

View More Posts
Go to My Shop
Related Articles
Bad or Rad: TNT
Bad or Rad: TNT
By Kevin Whipps
Are Geometric Shapes The Next Big Trend in Web Design?
Are Geometric Shapes The Next Big Trend in …
By Daniel Schwarz
Top Web Design Trends for 2016
Top Web Design Trends for 2016
By Maria Antonietta Perna
28 Comments
  • In my opinion and professional experience, web designers should know how to convert their design into CSS & HTML. I would highly recommend using a task automation tool such as Gulp or Grunt to help with front-end development. Another great tool is a template engine called Jade which makes coding so much easier. Saves you a lot of time and makes things so much cleaner. 11 years ago
  • Great article. I'm a designer who codes (not to be confused with a developer). I think a basic understanding of HTML, CSS and even a little javascript can be what separates a versatile, valuable designer. The ability to throw together a simple site on your own is a great skill to cultivate, if you have the desire and aptitude. 11 years ago
  • If designers should be expected to know how to code then developers should know how to design. It would only be fair, right? People have different skills and the area of web design has so many facets to it that I think it's ok to have specialisations. Do what makes you happy and what you're best at. If you don't like coding, then don't. I do believe however that having sufficient knowledge about how a website is actually built and what restrictions, limitations there are is important to understand at the very least. Knowledge is power as they say. Should an architect also build a house they designed? Probably not. But they should a solid understanding of construction methods, standards and limitations related to building. 11 years ago
  • It's a good question! Coding is a great skill to have, in my opinion, as a designer. It really opens the door with your design career. However, I realize not every designer has an interest in learning how to code. I think the key, as the article mentions, is to find that balance you like between designing and coding. Do what you like and you'll find success. 11 years ago
  • I don't know that designers need to know how to code, but they need to know some basics, especially about what works on web. I've made websites since 1999--both design and development. I started doing development for designers about a year ago, and a few designers I worked with had no understanding of how the web works. The web is NOT a business card or brochure to be printed once--websites need to adapt and allow for content to change, different screen sizes, and to load quickly. Nothing should be underlined unless it's a link. Things that aren't links shouldn't be the same color as things that are. Layouts should allow for content to be changed in the future without having to re-code the template because the designer demanded everything to be pixel-perfectly aligned based on the current content. These were all things I dealt with, and felt like a jerk telling designers--but they needed to hear it. So no, I don't think designers need to know how to code, but they need to understand how websites work (highly recommend Don't Make Me Think by Steve Krug), and what is realistic and practical on the web. And a basic understanding of HTML and CSS never hurt anyone--nor, on the flip side for developers--does a basic understanding of design. Because sometimes a designer leaves something out, and a developer may need to fill in the blank. 11 years ago
  • I believe that knowing at least a little HTML and CSS makes me a better-informed designer. it also means that I can speak to developers in their own language, which makes communication and collaboration easier. However, I have to force myself to sit through video tutorials and into attending workshops against my nature. I don't get excited by code in the same way I do with visual design. It's just how my brain is wired. However, I do enjoy the sensation of learning something new, which goes some way towards motivating me to code. Also, the desire to produce reliable, well-considered and effective designs also pushes me to learn. It is difficult to ignore the fact that both areas are interdependent. There's also another side to the debate; should designers do UX? It's my opinion that design, UX and development are all intertwined, and bleed into each other. As such it's good to specialise in one thing, but to have a little understanding of your partner disciplines as well. No one can know everything, so for more complicated projects, you'll surely need to be working as part of a skilled team of experts. 11 years ago
  • Designers not wanting to (or not wanting to expend the effort) to code is exactly why http://www.webydo.com/ was designed. It's designed to help designers create websites from a design frame of mind (and code free) without needing to involve a developer. I haven't used it yet - I just stumbled upon it and think the idea is worthwhile. 11 years ago
  • If you're designing websites having at least basic knowledge of how to code them will help you make better websites, and also communicate better with any developers that actually go in and code things afterwords. You don't have to be an expert, but knowing the basics and having a solid foundation will be very helpful. 11 years ago
  • Anonymous
    While been practical/learning the basics of coding is essential, at the same time, I feel a designer shouldn't let that cloud their vision. Why? I think as a designer, its better to come up with all the ideas that you can, that way you do not limit yourself with "can this be done" type of thinking. Articles that speaks about this subject : Article 1 - > http://joshuaseiden.com/blog/2013/08/designers-shouldnt-code-is-the-wrong-answer-to-the-right-question/ "Addendum #2: Some commenters are coming to the conclusion that I believe designers must code. I think that’s nonsense too. The world of digital design is big and varied. (And yes, many of us work beyond the web–gasp!) The skill sets required on any one project are too big to live in one body. So… multi-skilled people? Yes. Designers must code? Nope. (I think Davide Casali’s long article on this subject handles the question with some nuance" - Josh Seiden's - Article 2 - > http://intenseminimalism.com/2011/designers-shouldnt-code-the-digital-duo/ “ So, in the end, they should or shouldnt?” The summary, is that there’s no answer to this question. As I said repeatedly: it’s more complicated than that. The answer isn’t “yes” and isn’t “no”. The answer is “choose”. - Davide Casali - Article 3 - > http://ignorethecode.net/blog/designers-are-not-programmers/ " If you know how to write code, if you know how your design will end up looking in code, you have to be careful not to let that knowledge constrain your design " - Mike Rundle - Personally I know how to code HTML & CSS. At the same time, I try not let that constrain my mind when sketching out ideas or coming up with interface ideas. But who am I to say anything, after all, I didn't jump in the business world yet. At the same time I feel, I won't change my perception, especially after reading those articles. 11 years ago
  • No. No, no, no no. Design degrees and programing/digital degrees are not the same and for a reason. First of all, I truly believe a designer leans toward the artistic and a programer leans toward engineering. I tried to code a webpage once for about a week and wanted to blow my brains out. I do not think we should be promoting the professional world to combine these two skill sets. Coding alone could be broken down into multiple degrees based on HTML, CSS, JAVA Script, and every other method there is to build a website. These are huge areas of study that we are allowing work places to under estimate. It is frustrating enough to see job postings for people who know how to work all of these systems. Why should we then ask them to be a designer as well? The savant these companies are looking for are rare and should be paid well for their impressive resumes. Instead, this is becoming the norm and a single job with mediocre pay. "Need not apply if you do not have a graphic design or marketing degree and can code .net and php." To me, that is comparable to saying, "Need not apply unless you do electrical, plumbing, and masonry." Even marketing is bleeding into the design scope. And they are asked to code! Why are we allowing employers to make our professions unimpressive unless they come in a single multi-talented package? We need to keep these lines strong. If the education of designers and web developers changes, as it has started to at my alma mater, then yes, companies should start asking for these unicorns to come out of the woodwork. Until then, I feel companies are passing on a great deal of talent. An employer should not take a second rate designer so they can have the benefits of coding and vice versa. To each his own. A designer is educated to be a designer. Notice there period at the end of that sentence. Anything more a a great plus, not the norm. I have to give credit to people who feel they are better designers or better at coding based on their cross profession experience. It is commendable and shows great motivation for growth. However, employers should recognize that this sensitivity can also grow from two people working together. I work with all sorts of people in all sorts of professions and not once have I met a challenge where the option to learn how to do the profession was better than learning how to work with the profession. 11 years ago
  • @sheena Perhaps what would be more accurate is that developers should respect the detail of a design and not try to change things, but when a designer hasn't specified what hover states or interactions (transitions) should look like, then maybe have the initiate to come up with something - I suppose that is a case where developers could be designers? Perhaps the rule should be: If the designer is not a developer, then the developer has to be a (bit of a) developer? Because: If a designer doesn't offer a *practical* approach, the developer has to create an alternative. 11 years ago
  • @Jonathan Mitchell interesting comment, as I've always thought that design and user experience are the same thing; after all, if the user experience is frustration then it's a bad design? 11 years ago
  • @Amber Smith Very true, there is a market there, but that market only exists because non-coding designers don't see the disappointing code that these WYSIWYG editors create. By disappointing I mean excessive and underperforming, and it saddens me to say that I can't think of one tool like Webydo that does it well. I was contracted to write a review of Webydo and I honestly couldn't do it, and many other similar tools as well. 11 years ago
  • @Rachael Metz I don't quite agree, however, I do see where you're going with this. Some employers take it to the extreme, expecting you to be the only designer/developer/illustrator/seo guy on the team. I for one don't like branding all that much, only the areas that cross over to design, and I won't waste my time with SEO. Building a website *requires* HTML, CSS and usually Javascript. Saying that you should/could have a degree for each of those would be crazy, you'd be 30 years old before you finally finish education! You can learn HTML/CSS to an expert level in about a month. Of course coding isn't for everybody, and if you don't want to do it, don't, but the idea that designers are artistic is a myth; the left-brain/right-brain concept is a complete myth. Aside from that, artistry is the least important aspect of being a designer. You can create a website as beautiful as anything but if it doesn't work well, doesn't offer a smashing user experience and doesn't motivate the user to interact, then it sucks. Every brilliant designer is a researcher at heart, not an artist. 11 years ago
  • "but the idea that designers are artistic is a myth; the left-brain/right-brain concept is a complete myth." I think I am actually quite successful in teaching my developer friends enough about the design principles that they can implement themselves. Things like negative space, size, ratios, etc. And then I showed them some steps they can use for 'artistic decisions' (ie. use popular color combos off of adobe kuler if you are struggling with color). Many of them are producing some beautiful sites with these steps. I'm literally watching them become 'designers'. In addition they pass on handy shortcuts for coding and useful plug ins and api hints for me to use. My sites are becoming lighter and more responsive to the point to where I feel like I can call myself a 'developer' soon. Honestly, to the point of the article title (and as we all figured out) there is no 'right' answer. I just personally feel more secure in the job market if I can say I can do both. I think @Daniel Schwarz hit the nail on the head about research - but this research actually happens because we are passionate about design. In the same way those who are passionate about developing are researching their field in depth to stay current in skills and trends. If you spread yourself too thin on any amount of fields then you won't be able to keep up with the nuances of all of them at once. 11 years ago
  • Anonymous
    "If you spread yourself too thin on any amount of fields then you won't be able to keep up with the nuances of all of them at once." Double thumbs up. 11 years ago
  • @Daniel Schwarz thanks for your comment Daniel. I still believe that both disciplines should have a good understanding of the other - in a 'practical' sense as you said. There are many aspects to a successful website - copywriting, UX, visual design, front-end, back-end, SEO, marketing etc etc. One person can't be expected to be an expert in all of them. But having an understand of how they all integrate and work together would be a serious advantage. As a designer myself, I always provide the developer with (in addition to the designs) a style guide of almost all of elements they will require throughout the site - colour palettes, fonts sizes, buttons, hover states, sizing guides, spacing guides and an explanation of an plugins or scripts that I believe will be required or that I'd like to be implemented. That way I'm not leaving it to chance or forcing them to make blind decisions or choices :) It's imporant to collaborate to get the best result 11 years ago
  • @sheena I'm curious, do you sample interactions as well? I use Atomic.io to copy designs over from Sketch. You should try it if you haven't already. It's web-based so you know the animations/transitions are completely feasible. 11 years ago
  • @Daniel Schwarz I haven't come across Atomic.io, but might check it out. Thanks. To be honest I haven't tried sketch properly yet. I'm happy using adobe products for now at least ;-) 11 years ago
  • @sheena Atomic.io isn't only for Sketch users, tbh you can use it for user interface design as well as interactions if you want to keep the workflow in a single app. 11 years ago
  • As a designer I learned how to code, I even enjoyed it. So yea, it helps in to understand the limitations. I've seen a lot of bloated code due to designers throwing their dummy out of the pram and insisting on stupid design features. Designers who can code, can often get around code bloat and help developers think of another way. Same for developers who speak to designers. I agree with @sheena I also think developers should have an understanding of design, and a lot of them do. Collaboration is the key. I disagree with @Rachael Metz that is just a stereotype of a designer and developer. The designer being a tortured genius and the developer an engineer, please. 11 years ago
  • I hate these questions because they just say "designers", ignoring the type of designer someone is, the media they work in, what kind of work they want to do, etc. Someone who wants to design print ads has no need to learn how to code. 10 years ago
  • Unfortunately, it's a moot point because most employers want Graphic Designers to code. If your brain can't learn it, you're done for. Time to find a new career. On an unrelated note: I heard that NASA expects their rocket scientists to be able to perform brain surgery. 10 years ago
  • Anonymous
    As a developer and programmer with design backround, I think that designers should know how web works. Just like designers are taught how to design print graphics in print technology in mind, web design should be also made with the technology limitations in mind. 9 years ago
  • Anonymous
    As a designer first and coder second, my employer at the agency I work at finds it invaluable that as a designer I understand code. And I agree. Whether or not I'm actually coding a website project is irrelevant, as long as I know how to and have a decent understanding of how code works, I have a huge advantage over those who don't. Having knowledge and experience with code effects how I design a website. And the end result is a better website. 9 years ago
  • Each side has its own process and presents its own challenges. Development is left brain thinking. Design is more right brain. Very few people are experts at both. I believe if you want efficiency and productivity you will focus individuals on a team to perform on their strengths. Strong developers who have to design don't usually put out the best solution. Strong designers who have to code (and I'm not talking about basic html and css–because most designers these days know that much) are not as fast as those who do it full time. I like to compare it to hiring a wedding photographer. Would you have your photographer also officiate and coordinate your wedding? Probably not, even though they may be capable of doing so. Just because different roles are part of the same event/project does not mean that they should be taken on by the same person. Hire the expert in the area that they are fully knowledgeable in. It prevents a lot of stress and headache down the road. 9 years ago
  • Great post, I think every kind of knowledge is important, with, or without usage in every-single-day. 9 years ago
  • Totscart, offer you a range of pram for baby which keeps your infant safe, and also offer aesthetics that make your infant stand out in a crowd. Get baby prams here online at the best price. https://www.totscart.com/prams 6 years ago