Are we still talking about this?

Today my Twitter feed is jam packed full of the same old ‘designers should code’ discussion. What frustrates me most about this argument is what non-coding designers have to say in their defence. Using the fact that architects don’t become listed engineers or pointing out that painters can’t build houses as a defence is so far off the point. I know the fundamentals of code but I am far from fluent. For me, it’s not about not learning to code, it’s about choosing the option to focus on other parts of my job that will help me to become the type of designer I want to be.

Last year when I began studying my MSc there were two options I could choose between — A masters in web design and development or masters in UX design. One of these would have involved improving my basic coding skills and the other would expand my learning in a different area of design. I chose the latter.

Did choosing to improve my knowledge of UX and passing up the opportunity to improve my coding skills make me a bad designer? Hell no. It just makes me a different type of designer.

All of this must be confusing for young graduates. When I look at job descriptions for juniors I realise there is so much expected of them and there is no quick and easy way to learn it all. If I could give a young designer any advice I would tell them that learning a new skill or tool helps you to design better or communicate more effectively then focus on learning that.

If you are still learning new things then saying “no” or “not now” is ok too.

And sure, for us non coders it’s very possible that some amazing designer with incredible coding skills is going to come and snap our jobs up because we can’t code… It’s also just as likely that she will replace us because we wasted all of our time arguing an issue that is moot.

Can we talk about something else now?