quote: Original post by Edward Ropple
I'm a little surprised at the answers. I would recommend that programming knowledge is second only to writing in this, myself.

I agree. (Although on a more abstract level, rather than putting programming as an absolute second.) If you want to be a good designer, you need to appreciate the abilities and limitations of the other fields. No point designing something that is impossible for a programmer to program, or an artist to draw, or your audio person to record, or for your modeller to create in less than 1m polygons. It's all very good saying that these skills aren't technically part of being a designer, but design is about inventing blueprints for implementation: if you don't understand implementation, then your design is worthless.

(PS. Sorry for digging up old posts: I just got back here after a month of No Net Access...)




Edited by - Kylotan on November 10, 2001 7:30:16 PM