4 ms·
Of course, we could just turn this around entirely and ask the UX guy, "Why can't we add feature X?" And his response could just as well be: "I don't know. I ju
by teilo 17y ago
Of course, we could just turn this around entirely and ask the UX guy, "Why can't we add feature X?" And his response could just as well be: "I don't know. I just design UI. I don't code it."
UX doesn't make you dumber. We really need the UX guys, but what we don't need is to compartmentalize them from the developers. This is a two-way street. UX needs to understand code enough to be able to read it and follow it. Coders need to be able to work within an existing UI design and not make it suck if they need to extend it or change it.
I have seen this work REALLY well. But what will break it every time is the "not my problem" attitude expressed in this post. It's not the fault of the UX paradigm when people abuse the necessary separation between design and code.
- gb 17y agoExactly. I'm an "interaction designer", basically a combination of the two; I design and code the UI. Often there is someone directing the overall UX, but the nitty gritty specifics of the UI functionality are my department.