How can we make computational design and code understandable to design students, and how can they define the designer’s role in regard to coding? I was recently explaining to a student the importance of timing when a project responds to a user – a difference in milliseconds can make a big impact. We were also talking about how designing and developing code requires a different way of thinking and abstraction compared to visual design. In interactive design, the 4th dimension of time and the definition of behavior in code is very different from the see-it-all gestalt one can get from looking at and refining a 2D visual design.
I think the way to go is to cast it in terms of designing behavior. There are many principles and concepts of designing interesting, rich, meaningful behavior that I think could be developed, some of which is instantiated in code, other aspects in the mechanical design (the turning of a doorknob or the page of a book for example), and others in the conceptual design. This shift to behavior design as an overarching concept that encompasses computation may make it more interesting and relevant to designers.