Why Designers Should Code (But Shouldn't Push Code to Production)(jlzych.com)

almost 6 years ago from Jeff Zych, Head of Product Design at LaunchDarkly

  • Ben Henschel, almost 6 years ago

    Why is implementing my designs in code not a good use of my time?

    I make a lot of design decisions while in code.

    My perfect headers in photoshop/sketch are now too long in a browser with real data, how should I handle that?

    Empty states, loading states, what if there is only 1 item does my design still look right.. etc.

    Code is just a tool, same as photoshop, sketch, a sharpie, a pencil. For me it's a tool that lets me be closer to reality and gives me control to ensure that everything is consistent and the best design possible.

    Plus I enjoy coding, it's fun.

    11 points
    • Jeff Zych, almost 6 years ago

      Great question. Like you, I've done a ton of designing in the browser. Sometimes it is the best place to make a design decision. In my experience, this most often applies to really minor things. Flows, layout, colors, etc., are best decided and more quickly iterated on in other places (Sketch, PS, paper, etc.).

      At Optimizely, we've built out a frontend framework for our product that defines common components like buttons, tabs, modals, etc. This means a lot of those really minor decisions that get made in code have already been made. Our product designers can focus on the big problems, like how those low-level components are assembled, what the user flow is, etc. This saves a lot of time for everyone, and makes the UI more consistent.

      And ya, coding is fun :)

      2 points
      • Tom BradyTom Brady, almost 6 years ago

        Static mockups only go so far. UX is much easier to figure out when you're creating/testing with the native medium. Coding is also nice because it gives you more time with your designs.

        2 points