More often than not, design is seen as merely aesthetics. Many organisations separate design from the development process, with designers handing static screens and prototypes to engineers — and in worst-case scenarios designers and engineers don’t even sit together. In the world of interactive design, functionality should play a significant role in the design process.
Code shouldn't hurt your creativity. It should enhance it.
— Benjamin De Cock, on Let’s Move
Knowing how to code allows you to make smarter decisions as a designer, it will help you to bring additional value to your work and projects. You don’t necessarily need to write production-ready code, but you should at least know about it as you will gain an understanding of the challenges an engineer faces.
Now… should engineers design? Isn’t the opposite true? I’d say maybe not designing screens per se, but they should definitely be part of feedback calls with customers. Listening to those calls help us better understand how the user feels about the product, what are their pain points, and what are the bits they love, so everyone benefits.
I’d say 25% of the real design work happens after a designer hands off their designs. That’s when engineers start pressure testing your designs, and they’ll find new constraints and edge cases you never expected.
— John Saito, on How to stay scrappy
We spend hours designing for a medium that’s interactive and responsive, but we start by producing mockups that are static and inflexible. If great design is not only aesthetics but also how it works, then it’s time to make development part of the creative process.
— Jeremy Bell, on Designing with Code
So that’s my take on the “should designers code” debate. In the end, it's not about your job title, but about your responsabilities. Remember, code is just another tool, and if it help you delivery better results, why not use it?
If you have any thoughts you want to share, feel free to drop me a tweet.