• Nick WNick W, over 6 years ago

    As a little tangent, this is one reason why I believe in the 'designers should learn to code' movement/perspective.

    There's a range of values on the spectrum and I don't think you have to be a production level coder. It all comes down to communication. You have to be able to communicate your ideas. If someone builds it, you should take an effort to understand their language to a degree.

    I think the 'designers should learn to code' philosophy lends itself to a two key things: heavy prototyping (either code or some proxy such as a visual programming sofware like Quartz) and open lines of communication with engineers.

    Prototyping allows you to communicate in a way that's much more effective than wireframes, documentation, mockups etc., interactivity is very hard to communicate and prototypes are the closest thing to making that happen.

    A general knowledge of programming also allows you to communicate and better symp/emathize with engineers. Design isn't about dictatorship; it's about working within constraints and if you can better understand those constraints, you can (potentially) create better solutions. And if they're bad engineers, you can call them on their bs.

    1 point