Linked by Thom Holwerda on Tue 27th Jan 2009 13:46 UTC
Thread beginning with comment 345812
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2007-11-17
Fully agreed.
My personal pet theory (attention, you are leaving the rational/scientific area now and are entering the armchair-psychologists lair!) is, that the whole discussion is so emotional, because non-developing users (e.g. the vast majority) feel helpless, one way or the other. Those who feel left behind by the changes pretty much by definition and those on the side lines appreciating the changes (that would be the "appologist brigade") who tend to engage in I-can-scream-even-louder-than-you discussions, probably because they feel this is one way to contribute, e.g. defending the developers.
I know. I tend to do so, too.
True. I'm probably more sympathethic towards the developers pov because I understand the mechanisms behind it due to first hand experience (never underestimate the motivating effects and the willingness to go an extra mile/code an extra hour because of a rapidly approaching deadline), but I hope that we (e.g. users, developers, distrobutors/packages, etc.) are able to learn from this experience to avoid similar destructive situations in the future.
I know that just because KDE 4.2 works for me does not mean that it will work for everybody, this should go without saying. Positive feedback cycles without filtering and constructive critisism are probably as counter-productive and dangerous in the long term as negative feedback cycles with a selective memory component and without the ability to reach an understanding between developer and user (although the former cycles are a lot more motivating for developers :-) ). I would probably have not responded to the OP had I not heard this "finally, the devs are starting to listen to their users" meme increasingly often in the last weeks.
I considered the negative cycle to be dangerous, because it tends to be memorised as a pattern e.g. disgruntled user complains and bashes a project -> project changes direction -> user concludes change happened beacuse of his reaction. It may be that I'm a bit hypersensitive in this area due to personal experiences, though
Please feel free to correct me whenever I march with the appologist brigade.
Edited 2009-01-27 19:37 UTC