36 comments

  • Duncan RussellDuncan Russell, almost 5 years ago

    WHEN WILL IT END

    42 points
  • Joel CalifaJoel Califa, almost 5 years ago (edited almost 5 years ago )

    This should be titled "Why I think designers shouldn't be the ones who implement their designs into production."

    Also:

    Design should be unrestrained

    Nope.

    40 points
  • Jim SilvermanJim Silverman, almost 5 years ago

    plea to mods: bring back the dead horse badge.

    27 points
  • Josh BakerJosh Baker, almost 5 years ago

    No more posts on this topic.

    15 points
  • Rick LanceeRick Lancee, almost 5 years ago (edited almost 5 years ago )

    Code is as far away from the user’s experience you can possibly get.

    http://i0.kym-cdn.com/photos/images/newsfeed/000/173/576/Wat8.jpg?1315930535

    12 points
    • Mike Wilson, almost 5 years ago

      What's wrong about that statement?

      Command line is no longer used by the general population because GUI is a far better user experience.

      Please tell me more about your product that requires it's users interact with your code to use.

      1 point
      • Ashley CyborskiAshley Cyborski, almost 5 years ago

        The statement is pretty backwards. Sure a user may never look at or touch your code, but that code renders a visual interface in the browser, that either is or is very similar to what they will ultimately be interacting with.

        Additionally, it implies that other methods of designing are "closer" to the user's experience, but a user will likely never see your static comps or whatever else you create to hand off for implementation. And since those things are inherently not the thing your user will ultimately be interacting with, they are in fact, farther from the user's experience than rendered code.

        0 points
      • Rick LanceeRick Lancee, almost 5 years ago

        Command line is no longer used by the general population because GUI is a far better user experience.

        Code has nothing to do with command line vs GUI.

        You don't need to interact with code to have it effect a users experience, a users experience does not have to be interactive, for instance: is an app or site that runs below 60fps or has networking problems good for the users experience? No. you fix this with writing good code.

        0 points
  • Luis La TorreLuis La Torre, almost 5 years ago

    You obviously never tried Framer.

    11 points
  • Dan GDan G, almost 5 years ago

    Clickbait title + tell me more about how I should do my job.

    9 points
  • Ben Henschel, almost 5 years ago

    Doesn't constraint increase creativity?

    I'm building products, not designing mockups that can't be built given the resources currently available. The user doesn't give a shit about how amazing my beautifully, unrestrained design is.

    Also really tired of this topic.

    8 points
  • Wes OudshoornWes Oudshoorn, almost 5 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.

    So...

    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, almost 5 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
  • Jorge ManchenoJorge Mancheno, almost 5 years ago

    beatingadeadhorse.gif

    I look forward to the day a downvote option is finally added to DN so this kind of story doesn't somehow make it to "Top Stories."

    5 points
  • Kwang-Su KimKwang-Su Kim, almost 5 years ago (edited almost 5 years ago )

    Conclusion — All designers who can code are restrained.

    5 points
  • Ray WangRay Wang, almost 5 years ago

    Is it ever good to be completely unknowledgeable about a skill that affects your end product?

    No

    4 points
  • Mike MaiMike Mai, almost 5 years ago

    Nice ad, Weld.

    4 points
  • John PJohn P, almost 5 years ago

    "In Praise of 'The Ideas Guy'" would be an alternative title for this article.

    4 points
  • Mike PropstMike Propst, almost 5 years ago

    "Designers shouldn't code. By the way, have you considered buying my product, which coincidentally lets designers build websites without coding?"

    3 points
  • Ashley CyborskiAshley Cyborski, almost 5 years ago

    So basically you've put yourself in a creative box and you can't think outside of it?

    And also, how is photoshop/illustrator/a whiteboard closer to the user experience than "code"?

    3 points
  • Alec LomasAlec Lomas, almost 5 years ago (edited almost 5 years ago )

    While coding and design are often intertwined for me (as in, they are essentially the same process), that doesn't have to be the case. Knowing, or even being required to, code does not preclude you from being able to create purely visual designs, and vice-versa.

    Also: design isn't just how it looks, it's how it works. If you think code isn't part of that, you're mistaken.

    2 points
  • Jonas S, almost 5 years ago

    Next week on DN: Flash is bad.

    2 points
  • Eric REric R, almost 5 years ago

    How many times will this exact article get written?

    2 points
  • Pete MillerPete Miller, almost 5 years ago

    "Example: if you’re building a mobile app, it should be designed on a mobile phone." So, like, designing in the browser ...with code...?

    1 point
  • Thompson GeorgeThompson George, almost 5 years ago

    Why I think I'll be unemployed.

    1 point
  • Ed AdamsEd Adams, almost 5 years ago

    There are other topics you can write about.

    1 point
  • ポール ウェッブポール ウェッブ, almost 5 years ago

    ಠ_ಠ

    Medium articles shared to this site are 90% shit. Also, thanks to Shrugster keyboard, I can quickly find my exact reaction to inane buffoonery like this.

    0 points
  • Chris CChris C, almost 5 years ago

    At least he inadvertently admits to his title being clickbait in the first sentence

    I strongly believe that designers shouldn’t (have to) code.

    0 points