Why Designers Should Learn to Code (and Developers Should Learn Design)

I have the odd title of “UX Developer”. Well, at least some people would call it odd. I don’t see it as odd at all. In fact, I think every team should have a UX Developer. The unique skill that comes with someone that’s able to both design and code is very valuable. It means designs aren’t made in the vacuum of the unrealistic. It also means the code executes in tandem with the intentioned design, rather than just the pixel by pixel literal interpretation of the mockup — which is especially useful when requirements change and when the reality of the technical debt involved comes back to haunt the deadline. It means tightening the feedback loop from design to implementation.

Now all this doesn’t mean there’s no room for just designers, or just coders for that matter. In fact, that’s just as valuable. Having someone dedicated to designing means you can benefit from more out of the box thinking, breaking away from what’s been done before and getting a unique perspective. Similarly, having people dedicated to coding means having higher level technical vision and focus for the tech stack. In general, having people dedicated to each discipline means healthier designs and healthier code, respectively.

But the key ability that a UX Developer brings is that unique ability to connect the dots between product design and implementation. It means worrying less about pushing pixels and more about pushing products — shipping!

It’s rare to find someone that’s able to do both, but when you do, embrace it! Empower them to do both and get refine their skills in both. They may not be the best in either discipline, but the unique ability they bring to do both is incredibly powerful.

So, if you’re a developer, I encourage you to learn some basic design skills. And, if you’re a designer, there’s really no reason not to learn to code. Adding the corresponding skill to what you bring to the table will make you that much more valuable!