5 ms·
Personally I'm happy to make an argument that given a lack of evidence that gender plays a negative roll, we have a moral imperative to eliminate unfair and dis
by kasey_junk 10y ago
Personally I'm happy to make an argument that given a lack of evidence that gender plays a negative roll, we have a moral imperative to eliminate unfair and discriminatory barriers to entry because its the right thing to do.
But lets say that isn't a compelling argument for you. Our industry has a disastrous success rate. Something is wrong. Most software is not getting written correctly, on time, or on budget. On top of this, it is nearly impossible to fill positions with qualified applicants.
Given that, there is a pretty strong argument that we should change the way we hire software developers and an obvious way to change it is to be more inclusive. If the current population isn't getting the job done, lets open the population up to others.
- tmnvix 10y ago> Something is wrong. Most software is not getting written correctly, on time, or on budget. On top of this, it is nearly impossible to fill positions with qualified applicants. True. > Given that, there is a pretty strong argument that we should change the way we hire software developers and an obvious way to change it is to be more inclusive. What is this 'strong argument'? Your conclusion "be more inclusive" is based on nothing more than an assumption that change will be good. There are any number of changes that could be made. You need to expand on your reasons for asserting that 'being more inclusive' will fix the problem. It could just as easily make it worse. You could possibly argue that increasing the pool of candidates by not excluding people based on irrelevant factors (such as gender, race, or age) will mean that we have a better chance of finding qualified candidates. The danger here is if we confuse increased diversity in the hiring process (opportunity) with increased diversity amongst employees (outcome). The first fits your assumption. The second doesn't and could lead to worse outcomes (from a business perspective).
- kasey_junk 10y agoThe argument is we could hardly be worse. I'm not convinced we know what qualified even looks like. We certainly can't tell in any objective way. Given that a purely random inclusion of more applicants is likely to improve the situation. Thats before arguing for the merits of a diverse work force or relying on moral imperatives.
- tnones 10y ago"Diversity" and "inclusiveness" isn't about adding more randomness to a selection, it's about introducing an explicit and deliberate bias. Special outreach programs favor candidates with lower _distribution_ in the available populace. Not only is it discrimination by itself, against the current majority, but it's self-defeating measure, in that every diversity hire skews the remaining pool of candidates more towards the biased majority it's trying to eliminate. This is usually combined with a concerted effort to ignore the actual sources of skew in the first place, because the implications go against ideas of blank-slatism and politically correct thought. If you want to bring moral imperatives into it, one would think a basic commitment to truth and statistical literacy would be included, but it very rarely is. You'd also imagine diversity of thought would be included as a point of intellectual honesty, but in practice, it is the exact opposite. As for software projects routinely failing, that has numerous possible explanations. One is that it's one of the most abstract forms of engineering around, in the sense that the material we manipulate and the arrangements we construct cannot be seen or touched, and hence are invisible to outsiders. It must rely entirely on explicit and deliberate communication, unlike more practical fields. The onus is entirely on the engineer to make himself understandable, and it is rare to find people gifted both in abstraction and verbal thinking. Another is the recurring observation that schools are particularly bad at teaching the practical skills required to deliver software projects, being taught by people with little to no industry experience. It goes beyond basic project and code management skills and goes into product design and usability: people learn to build code when they should be learning to craft tools. But just because currently applications focus more on theory than practice, doesn't mean we'd get better results by turning to people who lack the theory entirely.
- kasey_junk 10y agoWomen have a lower distribution in the populace?
- flukus 10y agoNo one is hiring from the population at large, they're hiring from the population of software developers.
- flukus 10y ago> we have a moral imperative to eliminate unfair and discriminatory barriers to entry because its the right thing to do. First you have to demonstrate that those barriers exist.
- throwaway729 10y agoFrom the article: "After drawing on data from thousands of technical interviews, it’s become clear to us that technical interviewing is a process whose results are nondeterministic and often arbitrary. We believe that technical interviewing is a broken process for everyone but that the flaws within the system hit underrepresented groups the hardest… because they haven’t had the chance to internalize just how much of technical interviewing is a numbers game"
- flukus 10y ago> because they haven’t had the chance to internalize just how much of technical interviewing is a numbers game Which means the barrier is themselves, not discrimination.
- Pyxl101 10y agoI have not read the entire article, but claiming that the process is nondeterministic is not the same as claiming that the process is discriminating unfairly by gender. If everyone plays the lottery, then some people will win randomly. Certainly if a hiring causes people to "win randomly", then it's not a good hiring process -- but neither is it a process that discriminates on gender. The article goes on to explain that, although people's interview performance is subject to variance from interview to interview, it does seem that interview performance is clustered around a person's average.
- codinghorror 10y agoHiring from all over the world and not just from "elite" universities would be the absolute first place I would start.
- derefr 10y ago> Most software is not getting written correctly, on time, or on budget. Oh, sure it is. It's just that the business-people and/or clients driving the projects want "fast and crap" rather than "slow and well-made", because "fast and crap" still makes money. Engineers (as in, people who have an engineering mindset, in any profession) will naturally fight back against this, which is where the time and budget creep comes from: theoretically, all software could be made "on time" and "on budget" and would be exactly as half-baked as the business-people were expecting it to be (and they would still be able to sell it, believe me.) But instead, engineers want to make something good, despite only having the time- and money-budget to make crap. Thus late nights and burn-out; thus unmaintainable hacks to get features "working for real"; etc. The problem is fundamental to the collision between these mindsets. Remove either, and the problem goes away. Software can be made using "pure engineering" (see NASA) and succeed. Software can be made using "pure business concern" (see bottom-dollar outsourcing shops) and 'succeed' (at least in the sense it's measured by.) But there is no long-term healthy place on the spectrum existing between these two points.