4 Mar
2011
4 Mar
'11
8:26 p.m.
Alexandre Prokoudine wrote:
On 3/3/11, david wrote:
Ah, one of my favourite topics :)
The thing is that you don't break it down to a programmer that his app
sucks. You tell him how to make his app even better than it now is, in
a way that would keep his workflow more or less along the same lines
while improbing every other bit. And with time you can even convince
him/her to improve workflow. I've been doing that for years, and guess
what -- it works.
I'm sure it does. Just keeping in mind that how the programmer uses his
or her app may well be *so different* from how someone else wants to use
the app, it doesn't make the app better for anyone, it only makes it
worse for everyone.
BTW, I see lots of programmers donating time to program apps, but damn
view UI or usability designers donating time to design UIs. So perhaps
those who complain about "this app doesn't work the way I want it to"
should stop complaining to the programmer and try to get some
UI/usability designers to contribute?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
Bedroom
software developers have never had to learn to
eat their own dogfood.
Actually, that is why many of the apps are the way they
are. Their
developers made them that way because they do use them, often daily.
(Many open source apps came about because some programmer had an itch,
and scratched it.) It works fine for them, so why should they change it
to fit some "amateur's idea" of how the program should work?