Why I think designers shouldn’t code(medium.com)

8 years ago from Tom Söderlund, Product person and entrepreneur

  • Wes OudshoornWes Oudshoorn, 8 years ago

    There is value

    • in being without constraints.
    • in crafting your designs with code to see the results in the browser.
    • in production-ready code.
    • in messy code to quickly test something.
    • in developers who use Git, Vim and the command line.
    • in drag and drop site builders for non-technical people.


    How about we stop talking about should and shouldn't. Instead we could focus on which methods, talents and people can be valuable in different situations.

    Walt Disney understood this very well. He had roles for the dreamer, the realist and the spoiler. The following article contains very valuable information about this process and is recommended reading for anyone who is involved a creative process.

    Disney Brainstorming Method

    7 points
    • Tyler Cecchi, 8 years ago

      Yeah, the dreamer, the realist and the spoiler aren't different people, they're different mindsets a person should have when thinking about ideas.

      What the author is suggesting is that one person should come up with ideas, and then another person should implement their ideas, which is silly because people work best with they practice both the squishy conceptual problem solving and the more rigid how-is-this-actually-going-to-work problem solving. To say people should only do one or the other is non-sense.

      1 point