4 ms·

That is, of course, your right. I'm just telling you that if you genuinely want to convince an entire community full of people who disagree -- as opposed to for

That is, of course, your right. I'm just telling you that if you genuinely want to convince an entire community full of people who disagree -- as opposed to forcing them into a temporary, resentful silence via top-down policymaking -- you are going to have to have those detailed discussions, whether you want to or not.

exstudent2 11y ago
You are of course correct. As soon as he linked to Geekfeminism I knew we weren't going to be getting anywhere. That my point of view must be silenced at all costs is one of the main reasons why I would never support the Geekfeminism people. Contrary to what the parent comment states, he is most definitely not willing to question his own base assumptions and political goals.
- JoshTriplett 11y ago
  > That my point of view must be silenced at all costs is one of the main reasons why I would never support the Geekfeminism people. There's a difference between silencing a point of view and refusing to repeatedly have the same argument. New arguments need new information, and the vast majority of arguments in that area have been had already. That's some of the primary value provided by their wiki: a repository of past arguments and refutations, to avoid having to revisit them every time. Project mailing lists and other communication channels, for instance, are the wrong place for repeated introductory conversations demanding justifications for a code of conduct. And that's a very common problem. Considering I didn't start with the set of base assumptions I have now, and had to learn them over time, I'm always willing to question them. That I don't personally find any of your arguments even remotely compelling towards that end doesn't make those assumptions immutable. To explicitly state some of the assumptions that I suspect we disagree on: 1) If you refuse to exclude anyone from a project, then you're by default excluding people who are not willing to put up with a hostile environment. 2) Since you can't avoid excluding people, better to exclude people who make the project less welcoming. 3) Don't let the people you want to exclude write the policy. 4) Don't let the people who would fare just fine in a project without a code of conduct drive the requirements; get the requirements from people who wouldn't. Apart from that, the other reason I don't particularly care about having this argument here is that it's unlikely to have as much effect as having it elsewhere.
  - exstudent2 11y ago
    I don't see much point in discussing Geekfeminism. You see it as a valuable resource, I see it as a corrupting force in our industry. We're not going to come together there. As for base assumptions, I see we also differ wildly. Mine are: * Code quality matters above all else. * People that don't contribute code don't get a seat at the table. * There's no inherent value in letting as many people as possible contribute to the project. Quality over quantity. I'm leaving out anything having to do with feminism because we're not going to agree on anything about it.
    - JoshTriplett 11y ago
      Yeah, if you believe code is more important than people, rather than code existing to serve people, this isn't going to go anywhere. There's another assumption you're implying but leaving out: "The set of people who show up and contribute under those conditions will inherently be the best and produce the best results". And that assumption is subject to a lot of confirmation bias; if you don't set out to question that assumption, you'll tend to get results that give you no reason to doubt it, precisely because it's harder to notice the absence of something.
      - exstudent2 11y ago
        I believe people are A LOT tougher than groups like Geekfeminism give them credit for. Telling them to "get good at coding then come back and contribute" is actually better for people than "come on in, we focus on being super inclusive" or even worse "you don't code at all, but please chime in on our project". People need internal drive to excel, no external welcoming will make that happen. Coding well is damn hard, by its very nature it's not a very inclusive thing. Very few have the capacity to do it well. I prefer to focus on them than on the masses that will never be great coders. I don't think pretending like everyone can and should be involved is useful. I'm a minority from a poor background. No one encouraged me to code, I couldn't even afford the tools I needed. I would read computer magazines in the supermarket and write psudeo-code on paper at home. I'm now a very successful software engineer. Regardless of how unimportant you think my own experience is, it IS quite possible to succeed if you're talented and from an under represented group, no "safe spaces" needed. Just tenacity, an interest in the subject matter and self-drive.

exstudent2 11y ago

You are of course correct. As soon as he linked to Geekfeminism I knew we weren't going to be getting anywhere. That my point of view must be silenced at all costs is one of the main reasons why I would never support the Geekfeminism people. Contrary to what the parent comment states, he is most definitely not willing to question his own base assumptions and political goals.

JoshTriplett 11y ago
> That my point of view must be silenced at all costs is one of the main reasons why I would never support the Geekfeminism people. There's a difference between silencing a point of view and refusing to repeatedly have the same argument. New arguments need new information, and the vast majority of arguments in that area have been had already. That's some of the primary value provided by their wiki: a repository of past arguments and refutations, to avoid having to revisit them every time. Project mailing lists and other communication channels, for instance, are the wrong place for repeated introductory conversations demanding justifications for a code of conduct. And that's a very common problem. Considering I didn't start with the set of base assumptions I have now, and had to learn them over time, I'm always willing to question them. That I don't personally find any of your arguments even remotely compelling towards that end doesn't make those assumptions immutable. To explicitly state some of the assumptions that I suspect we disagree on: 1) If you refuse to exclude anyone from a project, then you're by default excluding people who are not willing to put up with a hostile environment. 2) Since you can't avoid excluding people, better to exclude people who make the project less welcoming. 3) Don't let the people you want to exclude write the policy. 4) Don't let the people who would fare just fine in a project without a code of conduct drive the requirements; get the requirements from people who wouldn't. Apart from that, the other reason I don't particularly care about having this argument here is that it's unlikely to have as much effect as having it elsewhere.
- exstudent2 11y ago
  I don't see much point in discussing Geekfeminism. You see it as a valuable resource, I see it as a corrupting force in our industry. We're not going to come together there. As for base assumptions, I see we also differ wildly. Mine are: * Code quality matters above all else. * People that don't contribute code don't get a seat at the table. * There's no inherent value in letting as many people as possible contribute to the project. Quality over quantity. I'm leaving out anything having to do with feminism because we're not going to agree on anything about it.
  - JoshTriplett 11y ago
    Yeah, if you believe code is more important than people, rather than code existing to serve people, this isn't going to go anywhere. There's another assumption you're implying but leaving out: "The set of people who show up and contribute under those conditions will inherently be the best and produce the best results". And that assumption is subject to a lot of confirmation bias; if you don't set out to question that assumption, you'll tend to get results that give you no reason to doubt it, precisely because it's harder to notice the absence of something.
    - exstudent2 11y ago
      I believe people are A LOT tougher than groups like Geekfeminism give them credit for. Telling them to "get good at coding then come back and contribute" is actually better for people than "come on in, we focus on being super inclusive" or even worse "you don't code at all, but please chime in on our project". People need internal drive to excel, no external welcoming will make that happen. Coding well is damn hard, by its very nature it's not a very inclusive thing. Very few have the capacity to do it well. I prefer to focus on them than on the masses that will never be great coders. I don't think pretending like everyone can and should be involved is useful. I'm a minority from a poor background. No one encouraged me to code, I couldn't even afford the tools I needed. I would read computer magazines in the supermarket and write psudeo-code on paper at home. I'm now a very successful software engineer. Regardless of how unimportant you think my own experience is, it IS quite possible to succeed if you're talented and from an under represented group, no "safe spaces" needed. Just tenacity, an interest in the subject matter and self-drive.