To see the relationship between a designer and developer, you must think of it in terms of relationship and how our cognitive processes work.
I'm not talking about knowing what tool you have to use to create a light/shadow effect, but experience in how certain rules applied to that instrument can create something that has a much more visual impact. I'm not talking only about Photoshop. This applies specially in the mind setting. I can create something with my mind, just the thought, the idea.
When you code, you have your instrument (computer, programming language, etc) you have to apply certain rules to match your design idea. But that's not all. With graphics, you can abstract datas (ie. idea), but programming you can pattern complex datas in a way that graphics can't do (ie. algorithms).
I'm in HCI/UIs and I design more than program, but that doesn't stop me love seeing (read: learning) code.
Comments
To see the relationship between a designer and developer, you must think of it in terms of relationship and how our cognitive processes work.
I'm not talking about knowing what tool you have to use to create a light/shadow effect, but experience in how certain rules applied to that instrument can create something that has a much more visual impact. I'm not talking only about Photoshop. This applies specially in the mind setting. I can create something with my mind, just the thought, the idea.
When you code, you have your instrument (computer, programming language, etc) you have to apply certain rules to match your design idea. But that's not all. With graphics, you can abstract datas (ie. idea), but programming you can pattern complex datas in a way that graphics can't do (ie. algorithms).
I'm in HCI/UIs and I design more than program, but that doesn't stop me love seeing (read: learning) code.
Paul Graham has a related essay on Hackers and Painters: http://www.paulgraham.com/hp.html