4,122 karma · joined December 8, 2008
I do think you need to start further up in your hiring funnel than the phone screen: were I in your shoes, I'd be trying to get more minorities to submit resumes in the first place. One of the problems identified by those studying diversity in tech is a self-selection bias: minorities, and women especially, seem to send out fewer resumes and less ambitious about the positions they apply to. Perhaps consider reaching out to groups like RailsBridge, Python Boston, PyLadies, Ladies Learning Code, etc., and letting them know you're hiring and want to talk to candidates from their communities? Drop me an email (and let me know where you're located) if you'd like me to try to help make you some connections.
Re-reading the above, I'm hoping it doesn't come across as critical; it's clear you're taking this very seriously, and that's awesome. Just hoping I can help more!
Really it's not. There's a big difference between active discrimination and just not caring. I said that my guess is that icedancer doesn't see lack of diversity as a moral problem, not that s/he is a engaging in discrimination. Accusing me of "jumping out of the bushes" to "attack dissenters" is really unfair. Look, I appreciate that some people don't see lack gender diversity as a problem. I disagree, but I'm never going to convince those people to see the issue in my terms. I hope you'll re-read my comment and try to assume just a tiny bit of good faith on my part.
In my mind, the Rooney Rule is a good policy to model after. Strict affirmative action is complicated, controversial, and... yeah, I'd feel "weird" just like you implementing hiring quotas. But an interviewing quota (or just a rough goal) seems perfectly legit.
The key is to focus on interviewing more women, not hiring more women. Do your best to get more women into the top of your hiring funnel, and you'll likely see more women come out the bottom. And you'll have a wider pool (because this'll force you to interview more candidates, total), which you'll have a better chance that whoever you hire — man or woman — will be awesome.
I see it like this: lack of diversity is a bug on our community. I'd like to fix it, so I work on fixing these bugs. Right now, the information I have available tells me that gender diversity is the worst of the bugs under the "diversity" label, and it's also one I think I have the skills to tackle. This doesn't mean that other bugs are less important, or less worth solving. I happen to believe that this bug is the one that's most worth my time to tackle.
Yes, I do see lack of diversity -- in all forms -- as an issue in our community. There are other minorities besides women that're systematically discouraged from entering tech; we should do something about that. Hopefully our fix for the gender bugs can be abstracted and applied in other areas.
Sorry, I must have not been clear: my point is that if we have twice as many people, then we get twice as much work done, move twice as quickly, etc. Django has about 30 committers, and among us we seem to be able to commit about 10-15 times per day. If we had 60 committers, I'd guess we'd be able to commit about 30 things per day. That's more bugs fixed, more features added, faster velocity between releases, etc. These are things I want.
> In reality, there is some reason why women don't want to be programmers.
I agree. I suggest that it's because women are systematically being discouraged from joining our communities. I think they's plenty of data to back this up.
BTW, it's not programming as a whole; the problem's even worse in open source communities. Women make up roughly 20% of the workforce in technical professions, but only about 2% of open source developers. Even if you believe there's something in that second X chromosome that disinclines women from tech — and for the record I certainly don't buy that argument — that can't explain why the problems ten times worse in open source.
> you would be much better served to use your limited capital to attract men who are already predisposed to your project but unaware of it rather than women who are both unaware of it and predisposed against it.
How about people who are aware and are predisposed, but have historically been discouraged or outright prevented from getting involved?
And look, this isn't a zero-sum game. I can do this and other things too! A lot of the resistance to diversity seems to imply that these efforts somehow detract from other forms of community outreach, but this just isn't true. We are in fact capable of doing multiple things at once.
The data I've seen suggests that the penetration of these minorities in technology closely tracks their representation in society as a whole. Further, there isn't a history of discrimination against redheads and lefties in open source. Discrimination against gay people is a real problem, though it doesn't seem to have prevented equivalent representation of gay people in tech.
But you could make a similar argument about representation of other minorities -- African Americans, say, or Hispanics, or whatever. And it's true, that's a problem too; we should be working towards diversity of all sorts. It's true that I'm focusing my attention of gender diversity, but I'd love to learn more about efforts towards diversity along other axes. Have any pointers?
Where, exactly, did I do that?
Let's say I have a open source project, and it's got 100 contributors (or community members, users, whatever -- the it's all the same). If my project follows today's averages, that group will be on the order of 98 men and 2 women. Let's say we work to increase our diversity such that now 50% of our community are women. How big is the community now?
That's right -- 200 people. It's not like adding 50% women removes 50% men... if we increase the number of women in our community, we increase the number of people. Now I've got twice as many contributors, twice as many users, twice as much activity, etc. Open source projects live and die on the strength of their communities. Increasing diversity is often actually the easiest way to increase membership, full stop.
[Now, in practice, I work on diversity because I care about basic fairness. But the point is that even if you don't give a shit about those sorts of ideals, there are still coldly calculating economy-of-scale arguments for why diversity is important.]
Say my "log in" test fails: OK, I know auth is broken... but what part of it? Is there some JavaScript hijacking the form submission? Is my login view busted? Do I have an error in my authorization system itself? Is the LDAP server I'm authorizing against down? Has someone changed the schema? Etc., etc., etc.
I do find functional tests to be a pretty valuable part of my testing toolkit, but unit tests seem to get me a bigger "bang for my buck", so functional tests tend to be something I don't spend a ton of time working on.
(I wish I did write more functional tests, but clearly they're not valuable enough for me to prioritize them. Otherwise I'd already be using 'em more.)
Anecdote time: last winter I started having serious, eventually debilitating knee pain. I went from 30-40 mpw to a point where even a couple miles hurt like hell. I have shitty health insurance and resisted seeing a PT for months, worried about the cost, hoping I could just "tough it out." Yeah, not so much. I finally saw a PT in January, got diagnosed with classic ITBS, and started rehab. Within a month I was back to 3-5 mile runs, and by March I was ready to run a half marathon. I'm keeping up with the strengthening exercises my PT assigned, and the ITBS is just a painful memory.
And the costs I was worried about didn't turn out to be much of an issue: my PT was willing to work with me and my crummy insurance to figure out a way to make it affordable. I only ended up paying about $250 for a couple months of visits — a small price to pay to be able to run again!
See a physical therapist!
It's really hard for me to see this as an "honest mistake"; it just seems more like your average, run-of-the-mill, laziness-induced plagiarism.
...
Or, with less snark: Instagram is fun. Using it makes me smile. Do I need a better reason?
Again, we gotta grow up. Yehuda's contributions to Rails 3 were important. What's wrong with taking credit for that? I'm often critical of the Rails community for an excess of ego, but this is not one of those cases.
It seems pretty clear that the idea of an open source developer asking for money seems vaguely filthy to a bunch of people. I think this is unhealthy and poisonous. It condemns open source to be the provence of academics, the unemployed, those able to snatch free time away from their friends and familier, or those working at the largess of their corporate employers. That's a shitty limit on the scope of free software.
What if Yehuda's company gave him 25% of his time to work on open source - would that be different? He'd get that same $25k (or whatever), and the software would get built (and open sourced). Only difference I can see is the source of the money, so are you against the idea of companies letting their devs work on open source?
There's this attitude in the open source world that somehow developers getting directly paid for open source is evil. This is -- excuse me -- fucking bullshit. I can't think of anything better than the idea of developers getting paid to write open source software. We need to grow the hell up and understand that paying developers to write open sourced software is a good thing -- open source devs get money, and the community gets software. Again, who loses?
I don't use Rails, and I probably never will, yet I kicked in some money to help see this through. I can think of about a million worse ways I could have spent that cash.
Yeah, see https://docs.djangoproject.com/en/1.4/ref/django-admin/#djan... and https://docs.djangoproject.com/en/1.4/ref/django-admin/#djan....
It's really very simple: you just create a directory of files and point startproject/startapp to that directory with the --template flag. Files are copied over into the new app/project, with some simple replacements for things like the project name.
You can check out Django's source for the built-in one, or if you poke around on Github you'll find some others. Here's one, for example: https://github.com/amccloud/django-project-skel/.
"Women" are being presented in a list of "great perks" -- along with "food trucks", "top shelf booze", and "dark chocolate". This is pretty much a textbook example of objectification.
This sort of objectification and othering is part of what keeps women out of tech, and that's a loss to everyone. More women joining our community means more people in our community, and that's a win for everyone.
>I can't imagine any of the women I know getting upset about that line.
Have you actually asked any women who work in tech about what it's like? Spending just a little time listening to what women in our industry think about the culture can be an eye-opening experience.
I'm not doubting that you can find women who aren't offended by this, but that's quite beside the point. It's essentially the "I have black friends so how can I be racist!?" defense — so laughable that Colbert uses it as a running gag on his program.
> So a genuine question, are we getting to a point where you need to think so much before actually saying anything? Personally, even if I were the butt of a mildly racist joke I would probably enjoy the joke than be offended.
If you think sexist and racist jokes are acceptable then yes, you probably should think twice before making jokes.
How exactly does one create a fact? That would be a neat trick.
> I'm sure you could have found a way to talk to web servers without waiting years for the WSGI spec to be finalized.
Indeed, we could have, and it would have benefited Django at the expense of diversity in the Python web world. It probably would have helped our "market share". But that's not how we roll. I'd rather work on something that the whole community can benefit from, and that means standards and specifications.
> And if Django had supported Python 3 using py-postgresql, which was released in 2009 [...]
That's true - I'd forgotten about that library.
> [...] others would have worked a little faster to make their database systems available on Python 3 as well.
That... I'm not so sure about. Volunteer community, limited by free time, etc. I'm fairly sure most people have worked on this stuff just about as fast as they can.
You do realize, of course, that the criticism here applies to you as well. If you feel this strongly you could have added a py-postgresql backend in 2009, you could have come up with a way to run Django under Apache and Python 3, etc. I'm happy to take a lot of the blame for Django's slow movement, but you're also responsible for not channelling your frustration into action.
> The reality is, everyone has basically been waiting for everyone else to make a move and it has resulted in deadlock.
I don't see a deadlock. I see steady movement -- slow, too slow, but movement nonetheless -- towards Python 3. First Python 3.0 came out, and it was horrifically slow, taking away any impetus to use it. So people fixed that. Then, developers ported the low-level libraries (database drivers, network protocol implementations, etc). Then we started moving to higher level libraries and tooling (numpy, wsgi, ...). Now the highest-level libraries (web frameworks, scipy, matplotlib, ...) are porting. Next, and finally, you'll get to port your apps. It's a classic dependency upgrade chain. You can't upgrade layer N until layer N-1 is done.
I share your frustration about the slowness, but that's frankly a characteristic of the Python community. We're relatively conservative, tending to prioritize stability and backwards compatibility over rapid movement. Everyone pretty much expected this process to take a while, and turns out they're right.
* Database drivers (psycopg2, MySQLdb, etc.) weren't updated for Python 3 until... last year some time, I think? Django supporting Python 3 is somewhat academic if you can't use a database with it, don't you think?
* The WSGI spec wasn't updated for Python 3 until summer 2011 (July, IIRC). Again, Django supporting Python 3 is pretty academic if you can't run it under a web server, right?
* The previous suggested approach for dual Python 2 and 3 support (using 2to3) proved to be untenable for Django [1], and it wasn't until this last year (or so) that a better approach (single shared source) emerged.
So to my mind, "as soon as possible" was something like July 2011. We had unmet dependencies before then; moving would have been... well, not impossible, but incredibly painful and nearly useless.
I will, however, take full responsibility for not getting Python 3 support shipped between then and how. Our current release workflow [2] got in the way, and about 7-8 months because of it. That's my fault, and if you want to rake me over the coals for those months go right ahead: I deserve it.
[1] Details omitted to be concise, though I'm happy to share them if anyone's interested.
[2] Which we're changing, mostly because of this silly workflow-induced delay.
In fact, that's exactly what we're doing. Django's going to support Python 2 for quite some time yet; this move will simply let those who want to switch to 3 do so.
> I don't understand what makes phraseology like this useful to anyone but a corporate lawyer: "the Django project is and will remain committed to achieving Python 3 compatibility"
Because we weren't clear that Python 3 support was in the pipeline some folks in our community started to wonder if we planned to move the Python 3 at all. That's pretty much the point of the post: to clarify that we do indeed plan to port to Python 3 (and when). How would you have worded it differently?
> Yes, I know, I'm not supposed to talk like this about work being done by volunteers free of charge.
That's not true at all: if you have substantive critiques to make, then you should make them. We try incredibly hard to listen to our critics and take away what we can. However, your criticism here is pretty thin and rather personal -- seriously, accusing a bunch of volunteers of being like Oracle or SAP? Low blow, man, low blow. It's hard for me to figure out exactly why you felt compelled to post this criticism, so it's hard to figure out what the action you'd like us to take.
> My anger is more about the Python 3 migration going off the rails in a way that poses an existential threat to my favorite programming language. Django isn't helping at all to say the least.
OK, so here we go -- there is something you'd like to see us doing differently. But what?
Sorry to bore you. Back to your regularly scheduled hacking.
* "Even 100k" implies that you think a six figure salary is reasonable for programmers. This is true in some rarefied echo chambers likethe Bay Area where programmer salaries are overinflated, but it's far from a universal The majority of our committers don't live near San Francisco. Actually, I think most live outside the US these days. I don't believe the median salary of a Django committers is 100k -- though for my fellow committers' sake I hope I'm wrong :)
* I only wish "being a core Django committer" was some magic "Get a Great Job Paying Six Figures Card". No good hiring manager assumes that "has a Django commit bit" translates to "among the most skilled engineers"; I only wish I could pull down "much more than" 100k based solely on my Django status. It's certainly a good time to be a Django dev, but while being contributor might help you get your foot in the door, it won't land you a salary increase over your peers.
* None of us get paid to work on Django anywhere close to full time. We get paid to do other things; we're lucky if we get a few hours a week to hack on Django as a side project. This again shows that our value in the salary marketplace isn't linked to our willingness to volunteer time to Django.
* Finally, this whole silly exercise assumes it would take "a year or two" of ALL of our time to get Django onto Python 3. That's laughable: it's mostly done already with perhaps a couple of man-months of activity. There's nowhere near 20 programmer-years worth of work; suggesting such is simply insane. Toss me that 100k you're bandying about so easily and I'll have it done by May :)