Programmer divide in IxD (was Help: Looking for another me)
14 Sep 2004 - 3:03pm
10 years ago
> on 9/9/04 12:01, Jef wrote: > You are correct to observe that knowing programming could interfere, as > you said in your full post: the designer anticipates a difficult > implementation and so might reject a better interface design. But there > is the opposite also. It has happened that a programmer has come to me > saying that something I proposed is too hard or impossible to > implement. Because I know how to program and am good at algorithm > design, I can show the programmer how it can be done easily, or at > least within practical bounds.
Sorry if this is responding to an old post from last week, I'm just getting
to a point that was made. I think this last statement is very strange. In
the context of these conversations about what makes a good IxDer, the notion
of telling a programmer how to do something easier is extraordinary.
It seems in opposition to some of the consensus of what is the >core> of
IxD. That IxD is design first. That the responsibility is to experience and
cohesion, before good code.
I'm not arguing with the value of programming. If you are really good at
everything and can do the job of the programmer then you're valuable to any
organization. I'm suggesting that the focus in the relationship between
experts-management. This hands-on approach is problematic for me.
Even Jef might back away from suggesting that what makes him a good at
designing interfaces is showing up his programmers. <grin>