| I agree that the original comment was not overtly _un_friendly. I also think that the reply represents a better way. > If the only way some one can give usable problem analysis and criticism is by including suggested fixes, I think we can all agree that the inclusion of suggested fixes does make feedback more helpful in general. > and delicately toning down the criticism, then far fewer people are going to be willing to expend enough effort to interact It does require a little additional effort to write kinder feedback, to take the moment to address the human being behind an Internet comment in a similar way to how we might address a person face to face. I'm as guilty as any of failing in that way. But if criticism's aim is to improve, it will be more successful if it's more easily digested by its audience. You catch more flies with honey than vinegar and all that. And really the reply above isn't that big a difference. In my view, it's a sign of intelligence, learning how to communicate effectively. If raising the bar only this high results in "far fewer people" interacting, maybe that's a good thing. I don't really need to hear from people unable to tame their own words when they have no time limit on typing them, and I'd rather belong to a community with fewer responses but a higher proportion of politeness and shared humanity than an array of comments expressing the kind of gruff emphasis on failure that bookends the original comment, "Your gif doesn't convey your idea __at all__," and "i'm confused as to why this project even exists." Edit: BTW today I learned "stet" thanks to you. |
I'm not sure why emphasis on failure is a problem, when that failure is precisely what is being communicated. However, the comment certainly does look a lot more unfriendly in light of the responses. Perhaps I was too kind to "i'm confused as to why this project even exists", because I don't understand why I would ever want "code snippets" myself.