This article was sent around my office the other day causing a little bit of a stir…5 Good Reasons Why Designers Should Code.

I think what caused the fuss wasn’t the actual content, but rather, the context it was sent in, i.e. by a developer to the whole company. It was seen as an insult, implying that the design team aren’t doing a good job, rather what it should have been, which was a comment on how we could all work better together. I do agree quite strongly that every designer should understand how websites are built. It can only be a good thing that the designer understands the capabilities of the tools to build websites, helping make best use of them to create a richer user experience.

On the other side of this though, the developer should also understand design. We can often battle against the belief that us designers are just styling. What we are really doing is attempting to create a good interactive user experience; considering a whole barrage of things, including content, structure, client brand, how to prioritise content and create visual cues, for example, by using contrasting or consistent colours and styles, using white space or even round corners to make it easier to distinguish between components.

Well, the list could go on and on, and I’ll hopefully get around to writing more on it another time, but the main thing to consider is that each member of a team has a role to play, and with good communication and understanding we would all create better websites.