91–100 of 160 posts
However, if you're a guy and asks something obvious like how to root your device (because it's a pinned topic in a sub-forum), be prepared to be flamed by a dozen or so users.
One can draw conclusions from all that, but I don't think it's really important as the Android community I help to admin does not factor gender when moderating discussions (though some of the general users might). I'll help a user regardless of who they are, not because of their chromosomes. I may not reply to a question or post for help because the information was discussed many times over and can easily be searched, but I won't flame a user for asking anyways. However, I will moderate those that do flame them because they should either ignore them or give a helpful response. I'm a huge believer in trying to seek out your answers first (if they're easy to find) and sometimes a user will never do that if you don't let them try on their own before providing assistance.
Android is kind of different though than many modding/hacking/tinkering communities. It's far less exclusive and developers inter-mingle with average users. Many times, it ends with the developer becoming introverted or ignoring users after a while because of general douchebaggery of the community or users (the community as a whole, not just the site I admin). Much of that though is from the developers just being too accommodating (https://news.ycombinator.com/item?id=4969041) and letting the users walk all over them for their generosity.
The community I admin generally tries to prevent user flaming (regardless of gender) and douchebaggery by users towards developers, but there's always some that happens anyways and users have to be put back in check. I get annoyed at some of these users and want to go off on them, but I just ignore them for the good of the community and be polite or ignore them when possible. A community is only as good as those that cultivate it.
Earlier quoted context omitted.
I just glanced at several of the headings, and it looks like that page is just a list of reasonable things to say.
That's the point.
To be fair to the author, she doesn't claim that everything is a result of sexism. The down-right douchebaggery is more apt a description for the majority of it, but there's no question that sex factors into big parts of it. There's a lot of egos in these communities, there are a lot of young people with adolescent hormones and something to prove. The communities themselves are pretty insular, and distinguish themsel…
There is a whole lot of derailing going on here. http://www.derailingfordummies.com/complete.html
To be fair to the author, she doesn't claim that everything is a result of sexism. The down-right douchebaggery is more apt a description for the majority of it, but there's no question that sex factors into big parts of it. There's a lot of egos in these communities, there are a lot of young people with adolescent hormones and something to prove. The communities themselves are pretty insular, and distinguish themsel…
There is a whole lot of derailing going on here. http://www.derailingfordummies.com/complete.html
>> He sat in on the crowd-sourced process of writing of the application, contributing nothing except criticism to anything I wrote for hours. That's the part of this post which really grabbed me. I went through the same sort of thing in a corporate environment not too long ago. I had suffered through discovering a massive security hole on an internal system, managing disclosure to just the right groups, writing the f…
Earlier quoted context omitted.
I understand what you're saying, but you may be in the (annoying) position that to back up your argument you'll really have to enumerate all those interactions and show the pattern. Drawing one anecdote without the context is less convincing than: "trust me, I experience sexism in the workplace."
"Unless You Can Prove Your Experience Is Widespread I Won't Believe It" http://www.derailingfordummies.com/complete.html#proveit
b: anecdotes dont' cut it
a: you are derailing the topic, here see this link
>> He sat in on the crowd-sourced process of writing of the application, contributing nothing except criticism to anything I wrote for hours. That's the part of this post which really grabbed me. I went through the same sort of thing in a corporate environment not too long ago. I had suffered through discovering a massive security hole on an internal system, managing disclosure to just the right groups, writing the f…
I'm going to piggy-back on your comment here solely because I've appreciated your comments in the past: There clearly are talented women in tech (and other fields, I know a pretty amazing CEO), and clearly this is a problem that a lot of men aren't "getting", in the sense that either they don't see it as a problem or they don't know what to do about it. Do you think there's an opportunity yet for some of the leading…
Yes. That won't back-fire. At all.
Earlier quoted context omitted.
>That's just one way sexism rears its ugly head at times in my experience Sorry but what in your story shows that it's sexism? It could easily have happened to a guy or been done by a lady security expert and is more a symptom of a superiority complex.
I'm mostly talking about the situation of reacting to the "wrapping" and missing the content entirely. The fact it comes from person X instead of person Y, and person X is not like person Y. When you see it enough times, you start hypothesizing about why it happens. Then you share notes with others in your situation and your hypothesis gets stronger. ... then you post about it to HN and have a handful of comments ins…
Well this is part of the problem. You weren't clear. You weren't clear in a way that other people asked you politely to clear up.
You turn around and accuse them of their own sexist behaviors.
When I read your initial description, it sounded like dozens of incidents that I have been party to when groups create documents.