Not designers.
Not coders.
Just builders.

Designers should learn to code. We’ve been talking about it for years, and the attention this issue rightfully earned brought about a change: designers are writing code now more than ever.

This movement has produced an interesting and unintended consequence: the line between designer and coder is blurring.

I propose we remove the line altogether.

Why? Say it with feeling: design concerns and code concerns are the same concerns. Internalize that for a moment. Designers and coders contribute to the project at hand equally—we both want the project to succeed. Because of that, our goals and concerns are the same.

Designers don’t want to build an app that runs slow because of agonizingly complex SQL. Coders don’t want to build an app that is hard to use. An incredible app requires both incredible code and incredible design. Without one, it’s not incredible.

Designers are tired of being the gatekeepers for visual detail and user experience. They’re tired of having to explain to the team that their concerns are not petty but are instead a major factor in a project’s success.

Coders are tired of dealing with designers who don’t understand how things get built. They’re tired of turning down silly features that have dire coding implications or are otherwise untenable.

Too often, designers and coders are at odds. Their interests compete. They disagree. If our goals are the same, the classic face-off between designers and coders needs to end.

The influx of coding designers proves we can do it. We can align our goals and start to alleviate all that mutual frustration by sharing our duties and skill sets.

Of course, specialization is important. If each of us were to just dabble in every possible skill rather than pursuing mastery, nothing would get done. However, we need to stop defining ourselves by too-narrow sets of concerns, and instead become well-rounded professionals who each excel in a specific area.

But there’s a problem: coders need to catch up. I could make a broad generalization that most coders don’t know about design, and it would be unfair but perhaps a tiny bit true. Instead, I’ll say that I don’t anecdotally know of many coders who understand even design basics. Do you?

Here is my plea: let’s all start learning about the opposite discipline and continue blurring the line between them. Designers: learn to code and understand why technical proficiency brings about great software. Coders: learn about design and understand why the little details affect the entire project. Let’s stop assuming our colleagues are out to undermine our interests and get on the same side.

Let’s stop being coders and designers—let’s become builders.

Perhaps too conveniently, I’ve written a design ebook for technical founders. If you’re a coder who wants to start learning design, it just might be a good place for you to start.

Written by Jarrod Drysdale. Follow me:

I'd love to hear from you; send me an email.

free eBook

From the author of Bootstrapping Design

Design's Iron Fist, a free eBook by Jarrod Drysdale

Thanks so much for reading this article. You can have my latest eBook totally free. It's a collection of my best writing from the last few years.

Learn how to:

  • Deal with doubt and fear
  • Think like a designer
  • Market an online business
  • Get out of a creative rut

14,000 words in a 90 page PDF with a custom layout design. Free, because I think you're awesome.

Enter your email address and I'll send it to you. You'll also receive my weekly newsletter.

No spam. Unsubscribe anytime.