The hackathon that they mention in the post (Mhacks) put up an application process and enforced a 50/50 gender ratio. In the weeks leading up to the event, I overheard many defeated conversations from fellow CS students over anxiety of getting rejected from this hackathon because they were male. The females didn't share the same anxiety, but it definitely made them feel down that they wouldn't be able to participate…
That's the dumbest barrier I've heard in a long time to enter a hackathon. Your gender shouldn't prevent you from getting into an event to get work done, it should be based on the merit of what you want to do. Did anyone ask if their rejection would be reconsidered if they chopped their penis off?
Hackathon Be Gone
61–70 of 143 posts
Re: Hackathon Be Gone
#62Earlier quoted context omitted.
Point is to get something done, force you to make choice, have a deadline, etc. -- not something else, like production ready code.
The older you get - the less patience you have for tight deadlines and 'forcing yourself to make a choice'. That's just having more energy than you know what to do with. The tragedy is young people have lots of energy and are scatterbrained and old people are sometimes wise but too tired. The future is having older wise folk write out proposals to ambitious projects, and have young people fill in the necessary parts.…
Re: Hackathon Be Gone
#63Re: Hackathon Be Gone
#64>If this sounds like advocacy for mediocrity, instead of merit, it is not. Keep in mind the following facts
And then follows up with a bunch of excuses about how they are not measuring merit by any means because traditional presentations and different project timelines are to difficult to compare for merit.
"it sounds like we don't want reward merit, and that's because we don't have the competence to measure it"
Re: Hackathon Be Gone
#65Re: Hackathon Be Gone
#66The point on marketing is spot on. I've seen team won first prize solely based on Powerpoint.
Re: Hackathon Be Gone
#67In addition to all the provided stimulants, hackers are encouraged to work through the night. Sure there may be reminders that you should sleep when tired, but why a 24- hour event instead of a 12-hour one then? Shut off the power and wifi from 10 PM to 6 AM.
Re: Hackathon Be Gone
#68Earlier quoted context omitted.
Point is to get something done, force you to make choice, have a deadline, etc. -- not something else, like production ready code.
The older you get - the less patience you have for tight deadlines and 'forcing yourself to make a choice'. That's just having more energy than you know what to do with. The tragedy is young people have lots of energy and are scatterbrained and old people are sometimes wise but too tired. The future is having older wise folk write out proposals to ambitious projects, and have young people fill in the necessary parts.…
Re: Hackathon Be Gone
#69The hackathon that they mention in the post (Mhacks) put up an application process and enforced a 50/50 gender ratio. In the weeks leading up to the event, I overheard many defeated conversations from fellow CS students over anxiety of getting rejected from this hackathon because they were male. The females didn't share the same anxiety, but it definitely made them feel down that they wouldn't be able to participate…
Re: Hackathon Be Gone
#70At Khan Academy we've been running ours as "Healthy Hackathons" — we kick people out at 11:45pm to get sleep, bring in healthy food, snacks, and activities, and always include our work week as part of the schedule (not just weekends). We actually just held our Monday-Friday Healthy Hack Week last week ( http://healthyhackathon.khanacademy.org ). One of my favorite weeks ever, particularly because we encourage "hacks"…
It's ironic that obviously very few Khan Academy employees have children of their own, but that's probably because it's only a few years since they were children themselves...