3 ms·
It's a little bit different on that side. Telling others to go fix things, if you succeed, is better than (just) doing it yourself. I can donate money to charit
by corin_ 13y ago
It's a little bit different on that side. Telling others to go fix things, if you succeed, is better than (just) doing it yourself. I can donate money to charity, but let's say my budget (and in other scenarios equate budget to time, or skill, or whatever) is £100/month, if I donate that and tell others to donate, then maybe I can have a £1000/month impact.
Whereas if I'm just telling people "this is no good, it needs fixing" then not only am I not helping, I'm not persuading other people to help either.
- coldtea 13y agoI see that as merely double standard. The main premise is wrong too: "if I'm just telling people "this is no good, it needs fixing" then not only am I not helping, I'm not persuading other people to help either.". Lots of things that are no good NEED to be pointed out. Project members don't magically see all of them. Either because they don't have that particular use case themselves, or because they haven't thought it that way, or they think it's not important but the users think otherwise, or they have invested too much in some design that they cannot admit it's flawed, etc. Pointing things out helps making those flaws visible, helps start a discussion, makes the opinion of potential or actual users known, etc etc. Telling people to go and help is very secondary to that. I don't think many people ever got motivated because of some second-hand meta-comment from someone not even involved in the project.
- corin_ 13y agoYou're absolutely right - when I commented I was thinking purely in terms of "you shouldn't tell others to get involved, you should be getting involved yourself", I didn't stop to think about the pros or cons of the original comment.