Do you need to code to be a designer
Out of context: Reply #9
- Started
- Last post
- 30 Responses
- nb1
A recent blog article on the subject:
https://medium.com/re-write/we-d…
We Don’t Need More Designers Who Can Code
What we should be saying is that we need more designers who know about code.
The reason designers should know about code, is the same reason developers should know about design. Not to become designers, but to empathize with them. To be able to speak their language, and to understand design considerations and thought processes. To know just enough to be dangerous, as they say.
This is the sort of thing that breaks down silos, opens up conversations and leads to great work. But the key is that it also does not impede the ability of people to become true experts in their area of focus.
When someone says they want “designers who can code”, what I hear them saying is that they want a Swiss Army knife. The screwdriver, scissors, knife, toothpick and saw. The problem is that a Swiss Army knife doesn’t do anything particularly well. You aren’t going to see a carpenter driving screws with that little nub of a screwdriver, or a seamstress using those tiny scissors to cut fabric. The Swiss Army knife has tools that work on the most basic level, but they would never be considered replacements for the real thing. Worse still, because it tries to do so much, it’s not even that great at being a knife.
- Article is longer, I just copy/pasted some of it.nb
- but the Swiss Army knife works perfectly and also forever, really bad analogy.uan
- Works perfectly? Try to open a restaurant and give the chefs a swiss army knife to prepare everything.nb
- Give that same Swiss Army knife to the servers to open wine with. See how long your restaurant stays open. haha.nb
- works at the right scale, the small one. if chef and server is the same person, it works. can't serve much plates with a small team though.uan
- It's a great analogy.monospaced