Eventbrite made this pretty confusing, as you can't waitlist more than 1 type of ticket (e.g. we couldn't waitlist male and female tickets). We'll come up with a better system for the next one.
Eventbrite made this pretty confusing, as you can't waitlist more than 1 type of ticket (e.g. we couldn't waitlist male and female tickets). We'll come up with a better system for the next one.
It seems there's only 2 ways to go when hosting an event -- open the floodgates or actively manage the attendee list. Because of space constraints, we had to go with the latter.
Managing attendees isn't just about restricting male signups, as you say -- it's also about making sure there are enough designers to developers, beginners to experienced coders, and yes, men to women.
I don't think that roguecoder is saying that this was the issue. This is a perfectly valid decision, considering all the logistical realities and your stated goal. It colors the implied message that there was a 50% split in interest between men and women, which is what I get from the blog post(which I do realize that was not the intent).
Unfortunately, I think that the blog post is misidentifying the real success here. It wasn't that you got 50 women. Your signup strategy pretty much guaranteed this. The hackathon could have been an utter failure, but the original goal would have The real success is that not only did you have an even gender split, you still had a very successful hackathon. That alone takes more work than just throwing up the signup page and limiting the signups to ensure that the proper distribution is reached, and I think should be the takeaway here: That it doesn't matter whether it's a guy or a girl.
> About a month ago, Hack’n Jill organized a hackathon with a simple goal: get 50 men and 50 women in a room to build something to improve their summers.
I don't see the problem with this. If you wish, you can hold your own hackathon without 50/50 male:female enrollment.
When did I ever say anything critical of their limiting attendees? If they want to do that, that's their business.
If they want to write a blog post about a bunch of tricks that might help your event be more inviting to women, that's great too.
The problem is with representing the results as due to those tricks while ignoring the other hugely significant factor (limiting attendees).
Consider this: how about I write a blog post about how I changed my headline color from red to green and got a 300% increase in sign ups. Oh, by the way, I also added a free usage tier at the same time, but that's more complex and I didn't want to include it in the same blog post. You should definitely use green for headlines, though.
"Looking at the figures shows that the picture is unambiguous. Not only are women doctors to outnumber their male counterparts in the UK by 2017, in general practice this will happen in the next four years. Entry data from medical schools show that over the past four decades the number of men entering medicine has doubled whereas the number of women has increased 10-fold."
http://careers.bmj.com/careers/advice/view-article.html?id=2...
And in my chair, 100% of mobile engineers are female. Woo hoo.
Now let's move on to your article. So much material there, where to begin!
We are feminising medicine. It has been a profession dominated by white males. What are we going to have to do to ensure it retains its influence?
Oh no, what are we going to do to ensure that medicine remains dominated by white males?!
There is a tsunami of women coming through.
Aaaaahhh... TSUNAMI! SOMEONE GET THE LIFEBOATS! Nope, doesn't sound hysterical at all.
I just believe that there should be NO discrimination whether positive or negative.
People should get a position based on their merit. If it ends up that a profession is all male or all female, so be it.
I would never spout a ridiculous angle such as 'child minders are predominantly female so lets make it easier for a male to get the job'.
You are imagining an idealized utopia. The problem is, we don't live there. Unless hiring is done purely through objective tests that have been tested for bias and normalized there will be social-status factors involved. Coping with those lets us get much closer to a merit-based world than pretending they don't exist.
Imagine you had some code but a system-level round function was broken: it rounded up on 4-9 and down on 0-3. You can't change the function without changing the entire operating system. Would the best approach be to say, "I don't think we should discriminate! Round functions should behave correctly!"? Or would it be to compensate for the known flaws while working to change the system-level issues?