A Martial Artist’s approach to the whole ‘should designers learn code?’ discussion(hackingui.com)

over 6 years ago from Sagi Shrieber, Co-founder of HackingUI.com, Creator of the Side Project Accelerator

  • Daniel De LaneyDaniel De Laney, over 6 years ago (edited over 6 years ago )

    Hi Sagi, I see you wrote the article. I wasn’t commenting on your point of view. I was commenting on the article itself. Specifically:

    • the rehashing of the ancient “should designers code” debate,
    • the What You Can Learn About Design From Anakin Skywalker title,
    • the empty arguments, and
    • the lack of proofreading.

    To expand on the “empty arguments” point:

    Plus, just know… Designers that know code, while they have the same years of experience than you and even less sometimes, will always be better designers than you. Don’t take it personal, it’s a simple matter of fact.

    It’s not a self-evident “simple matter of fact” that designers who code are better than those who don’t. If you want to argue your point of view in a convincing way, you need to supply reasons for your position, not meander through a story about cage fighting and then declare something unrelated about design.

    Sorry that my original comment wasn’t more helpful.

    Edited to remove comments that might be mistaken for engaging the question of whether designers should code.

    4 points
    • Sagi ShrieberSagi Shrieber, over 6 years ago

      If you can better communicate with developers - aren't you a better designer?

      You just proved my "empty" argument to be true for yourself.

      Design is a broader skill than knowing typography and the like. Its about communication. Communicating messages visually, communicating verbally with stakeholders, communicating verbally with developers. The world respects doers. Designers do. Coders do. If you can do both - you got the upper hand.

      2 points