Don’t start building that strawman, yet. I don’t believe in diluting the quality of an event just in order to achieve diversity. But I also refuse to accept that a decline in quality is a necessary result of trying to achieve diversity. In fact, just the opposite. All my experience as an organizer points to a properly organized diverse event being of higher quality than a monocultural one.
Let’s take the ruby world in particular, since that’s the concrete example on the microscope slide currently.
BritRuby started with 15 invited and 5 “open” slots for presenters, then filled those invited slots with 15 white males. Now, if I were picking my 15 favorite ruby presenters, I can’t imagine leaving off Sandi Metz (“Go Ahead, Make a Mess”) or Katrina Owen (“Therapeutic Refactoring”) at the very least (I’ve never made such a list, but they’d easily make my top ten). I wouldn’t end up with such a homogenous list without several people turning me down. I have no idea if that happened here, but available evidence (albeit hearsay) suggests not. And that’s unfortunate.
To be fair, I do not for one millisecond believe the BritRuby organizers to be evil, or even moderately chauvinistic, based on this list. I think more likely this is just one more example of the type of unconscious bias shown in that Princeton article: all of us are unconsciously biased towards selecting those in the pool more like us than others. In other words, I “accuse” the Brit Ruby organizers not of being ravening sexist misogynistic pigs, but merely of being human (and no less human than I, if it comes to that).
To me, diversity in a conference is a lot like tests for my code. I don’t write tests because other people want me to. I don’t write tests simply to have tests. I don’t have a specific number of tests in mind when I start writing, nor do I have a target number of tests per lines of code that I am expected to meet.
I write tests to make sure all paths through my code are exercised, and help me maintain that code in the face of changing requirements. My tests help me bring new developers into a project by helping them understand what the code is meant to do, and help non-developers understand what the code is doing, because the tests are easier to understand than the code.
Because of this, in order to write the tests I need to look at my coding task through other’s eyes, forgetting for the moment what I know about implementations and what I expect to do. I wasn’t always very good at this (in fact I used to stink quite badly at it, to be honest) and I still commit howlers even after all my focus on tests.
I rely on other people to see what I don’t. They have a different perspective on the code, so they see different things. After all, it’s not easy to look at code (or other things) from someone else’s viewpoint. Unless, of course, you *are* someone else.
And that’s the point. The more different from me someone is, the more likely they are to think of something I’ve missed, and I’ve learned the hard way that by listening to them I improve my ability to think of those things myself.
We all know “Linus’s Law” (“With enough eyes, all bugs are shallow”) and know its utility. But I’ve discovered that there’s a quality factor to that as well — that the more the eyes are like mine, the more likely they are to overlook the same things I do. I’d much rather have one pair that can see what mine don’t than a hundred pairs that see what I see.
Make no mistake about this, I’m not encouraging diversity simply for the sake of diversity. Like code quality in TDD, making everyone feel included is a byproduct, not the goal. I’ve a much more selfish agenda than that. Conferences with the same old guys giving the same old talks are boring. Hearing from minds different from mine, minds built from radically different experiences, strengthens my own, expands it, makes it capable of imagining bigger and better things.
Makes it into more of a tool I can build good stuff with.
found this paragraph around this site.
It is not my very first time to visit see this site, i am visiting this web site dailly and take good data from here daily.
All JORDAN’s 100% authentic, leather uppers are comfortable and durable, with built-in AIR-Sole air cushions, bringing extraordinary leveling effect, translucent rubber outsole with Jordan herringbone shading, creating superior grip and durability. 50% discount on quality, wholesale, please contact KicksOKOK online store service, fast delivery, good packaging, good quality shoes, good craftsmanship, sole wear-resistance, running shoes feel good elasticity, comfortable and breathable uppers, when running The foot bag is not deformed properly. However, due to the lack of owners, Jordan Shoes appeared to be alone and desolate. Therefore, it was looking for a buyer to take home. Buyer Features: There is a pair of size-matched ankles, with a sincere and kind heart. You are expected to become the owner of Jordans.