On Mon, May 18, 2009 at 1:05 AM, Joshua Muskovitz <[email protected]> wrote:
> What do you call someone who sits squarely on the fence between interaction > design and implementation? > By the way, Microsoft suggests ( http://windowsclient.net/wpf/white-papers/thenewiteration.aspx) that this kind of role is called "Integrator." I've also seen the terms "devigner" and "dezeloper" thrown around, but they're pretty corny sounding, IMO. I think the "integrator" role is actually pretty specific to XAML-based projects (as they frame it), so it's not quite accurate for someone who can/wants to work as a dynamic duo on other kinds of projects, and it also appears to be more technical "with design sensibility" rather than a full on skillset in both interaction design and development. In any case, I think the suggestion (by Mr. Spool, I think--hope I'm not putting words in his mouth!) to look at the required/desired skills rather than titles so much. Also, I think you may have to pick one or the other that appeals to you more (if that's the case) or that you have more visible experience in and take that on as a primary role while leveraging your skills in a secondary until they get to know you, at which point, if it is a good org you want to stay with, you may be able to fluidly move around as needed. HTH. -a ________________________________________________________________ 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
