• Jason MillerJason Miller, over 6 years ago

    Design is how things work. And code is what defines how things work.

    Of course, the designer doesn't need to be coding everything by hand. But we're responsible for communicating design intent to the people who write the code, and if we don't understand the processes and constraints that developers have to deal with, then communication breaks down and we design things that are difficult or impossible to build.

    0 points
    • Tyler Cecchi, over 6 years ago

      I agree, but I don't see how that invalidates writing code as design.

      If design is how products work, and code is what defines how products work, how is writing code not design?

      I don't buy that retro-fitting a 'classical' designer into an engineering mindset is the right way to design a product. I would have to think that it would be much easier and more efficient for engineers to adopt a product design mindset, seeing as they already use a ton design concepts when writing code.

      0 points
      • Jason MillerJason Miller, over 6 years ago

        You've got me backwards. I'm saying that writing code IS design.

        Or more accurately that code is the final expression of design, and so it's a design task to make sure that the design intent survives the development process.

        0 points
    • Sean LesterSean Lester, over 6 years ago

      I agree with this, and don't disagree with anyone who says that designers should learn SOME code — enough to understand how development works and what is possible, how to communicate design intention etc.

      I think, too, that good relationships and communication with developers in a collaborative effort will suffice, however. Developers appreciate being considered a meaningful part of the process and being collaborators, not just grunts who execute design.

      0 points