A new spin on an old chestnut. In “Designers Shouldn’t Code” is the Wrong Answer to the Right Question, designer Joshua Seiden succinctly articulates why some professionals fear that too much knowledge of code will lead to designs being based around implementation models instead of a user’s mental model; why that concern is overblown; and why having HTML, CSS, and JavaScript in the design workflow can make for a much better end-product.
Here at ALA, of course, it’s preaching to the choir. But Seiden’s quick, clear framing of the case makes it a fine article to share with colleagues who believe front-end code doesn’t belong in a “real” designer’s practice.
Like this:
LikeLoading…
3 Reader Comments
The topic discussed is really interesting and up-to-date! Thanks for touching it!
Thanks Jeffrey, for touching this topic! Many people view code as a restriction to a designer but actually it is liberating as it opens up a whole new realm of creative possibilities. Your design is executed the way you want it to be.
DbaiG
Bolee.com
Maybe designers should’t code, but they need to have a deep understanding how their designs can impact the code. Basically talking about responsive design.
Got something to say?
We have turned off comments, but you can see what folks had to say before we did so.
Every language app in your pocket inherited a teaching method built for Latin. Understanding why that happened is a more useful design lesson than anything the apps themselves can teach you.
Designers are good people. Some designs exclude people anyway. Alan Dalton offers a practical fix: accessibility personas that help you recognize problems while you're designing, not after. Homework included.
Computing was born in a Viennese café. Between 1928 and 1934, while Hitler plotted and Europe crumbled, a motley crew of mathematicians, philosophers, architects, and economists gathered weekly to puzzle out the limits of reason—and invented Computer Science in the process. What made their collaboration possible wasn't just brilliance (though they had plenty). It was amiability: the careful design of a social space where difficult people could disagree without destroying each other. Longtime Web Dev Notes contributing author Mark Bernstein mines this forgotten history for lessons that might just save today's embattled web from its worst impulses. Spoiler: it involves better coffee service and the looming threat of public humiliation.
Design systems aren't component libraries—they’re living languages. Rigid adherence to visual rules creates brittle systems that break under contextual pressure. Fluent systems bend without breaking.
The topic discussed is really interesting and up-to-date! Thanks for touching it!
Thanks Jeffrey, for touching this topic! Many people view code as a restriction to a designer but actually it is liberating as it opens up a whole new realm of creative possibilities. Your design is executed the way you want it to be.
DbaiG
Bolee.com
Maybe designers should’t code, but they need to have a deep understanding how their designs can impact the code. Basically talking about responsive design.