↵

John Maeda: If You Want to Survive in Design, You Better Learn to Code(wired.com)

over 6 years ago from Benjamin Valmont, Designer

  • Tyler Cecchi, over 6 years ago

    If you see writing code as simply factory-type production work, then you're just as narrow minded as the person who looks at "design" as simply aesthetics.

    Gap analysis, Market analysis, User analytics, Specification, Product strategy, Information architecture, Understand psychology and HCI, Apply psychology and HCI, Sell a solution, Scenario planning, Create a product vision, Prototype, Wireframe, service design, Create personas, Do user research, User interviews, Do stakeholder management.

    These are not designer skills. They're used in design, but not exclusive to people who:

    Create comps, Art direction, Understand motion design, Understand colour theory, Understand typography

    Many of the things you listed are shared responsibilities among product, design and tech. Building great products is a team sport after all.

    1 point
    • barry saundersbarry saunders, over 6 years ago

      I don't see code as simply factory-type production work, but I've rarely seen a business that's structured to take advantage of creative coders. Every designer / coder I've met has been frustrated by being pushed into production work.

      I agree that building great products is a team sport. Good design comes from creative tension between people with different specialisations. Which is why the constant push to learn code instead of all those other design specialisations is frustrating!

      0 points