39 karma · joined September 28, 2012
I like this article but it doesn't go into the positives of a CoC. There are many problems but if you don't weigh them against the positive characteristics, you don't see the full picture.
My organization NumFOCUS, asks all conferences and projects working with us to adopt some CoC. Why do we do this? First it has been shown in our community to help encourage minority groups to participate. Second it outlines a real procedure if something does go wrong. Finally, it sets the expectation of professionalism early.
Our numbers on diversity have skyrocketed as we enforces CoCs. It's not just a bandaid, it's an invitation to people of all types that we, the organizers, will protect your right to be at our event. I don't think event organizers are in any position to think they can solve all the problems in tech but at least they can create an inviting space.
Without a CoC, the procedure on how to handle a harasser is very grey. What legal grounds does a person have to tell someone to leave an event? If it is any grounds then why for some and not others? Who makes these decisions? I've seen conferences not deal with up front and have to resort to the local law enforcement to intervene.
Which brings me to my last point, set expectations up front. It's like the big silver punch bowl at the new years party. We expect you to be an adult and treat everyone else like an adult. A CoC clearly lays out that your event is intended to be professional.
I don't think it is the end of all discussions, in fact only the beginning. Our staff put together more things to consider, https://github.com/numfocus/DISCOVER-Cookbook, but a CoC is the simplist.
At the end of the day a lot of code uses NumPy and not Pandas.
Fashion Metric is changing the way people buy clothes both in-store and online. We're a math and data company tackling big problems with cutting-edge technology and we're looking to grow our team with smart, creative people.
Stack: Python + Docker + Cloud + undefined front end Compensation: $90K - $120K + equity
Perhaps this is what is desired (fixing roll over issue as well):
static int (**hget(int (**t)[2], int k))[2] {
int (**t_old)[2] = t;
int h = k & (SIZE - 1);
for (t = t + h; **t && ***t != k;
h = ((h + 1) & (SIZE - 1)), t += h, t = t_old + ((t - t_old) & (SIZE - 1)));
return t;
}Hate to have to tell all my Cython code it needs to break itself because the hackernews thinks so. =P
http://www.hpcwire.com/hpcwire/2011-12-13/ten_ways_to_fool_t...