[Sigia-l] Designers and Developers
Listera
listera at rcn.com
Wed May 26 19:28:37 EDT 2004
Boniface Lau:
>> If you are asking me, just two: Designers and Developers.
>
> Mind you, to produce something of good quality, a person has be good
> in both the design and implementation of the thing being responsible
> for.
Designers won't have to build/implement, developers won't have to design. So
I don't see where the problem is. Designers have to understand the technical
ramifications of their design choices. That's very different than saying,
designers have to be good programmers. They'll never have to write code.
> The emphasis on the separation between "Designers" and
> "Developers" will likely lead to less than optimal products.
Just the opposite: those who are actually trained/focused on design will end
up doing design and those who know how to write/manage code will do so. The
separation optimizes the expertise of the executors. I just don't see the
efficacy of asking developers to get involved in design/usability/etc *when*
there are designers to do just that.
>> So my dream is to see the Design and Development sides to
>> consolidate into two distinct entities bridged by the functional
>> prototype.
>
> And that prototype will probably become the "wall" that one group
> throw things over to the other.
Why?
Ziya
Nullius in Verba
More information about the Sigia-l
mailing list