Here's the key piece I took away from this: > [...] We as competent craftspeople should be able to communicate > with great precision and clarity what we intend the software to do > without resorting to code.[...]
The operative word here is "should." In the 15 years I've been designing interactions, most of it has been done w/o writing a single line of code. I've been able to show and describe most interactions w/ o coding. In practice, however, that's recently changed. I probably still could do it w/o writing any code, but I haven't been. In the past 9 months, I haven't done a single wireframe. That's right 0. Instead, I've been prototyping. Cheers! Todd Zaki Warfel President, Design Researcher Messagefirst | Designing Information. Beautifully. ---------------------------------- Contact Info Voice: (215) 825-7423 Email: [EMAIL PROTECTED] AIM: [EMAIL PROTECTED] Blog: http://toddwarfel.com ---------------------------------- In theory, theory and practice are the same. In practice, they are not. ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
