I HIGHLY suggest vetting the placement "statistics". For me, I just read 95% get a job, went to the open house, listened to a couple "rah rah" testimonials and did it. It was a big mistake.
A friend of mine from the class estimated that only 30-40% of us got actual dev jobs. The rest are either in customer service at a tech company, sales or testing (keep in mind this is people who dropped $15k+ to do the bootcamp), back in our old industry or in the case of one, working at Trader Joes.
I was under the impression that 95% get good jobs. If I had known only 30-40% did I would have never done the boot camp.
How did they manipulate the numbers? I never dug deep but here are my thoughts:
* to qualify as "actively looking" you can't have a job to support yourself. That's right you're supposed to not have an income while job searching, kinda hard when it can take more than six months. If you get a job, you get dropped from career support and your statistic gets placed in the "not actively looking" category
* "industry related jobs". If you go to a dev boot camp, you want to be a dev. You're paying $15k to do it. A customer service job at a tech startup is better than nothing but you don't have to pay $15k to do it. Likewise for sales.
As a positive point, all the females in our cohort got dev jobs, including the only one who actually failed the class. Startups are pretty aware of the gender discrepancy and actively looking to hire those with double x chromosomes. Not complaining about affirmative action, just wanted to give you as full picture as possible
Also I recognize that a forum is really not conducive to this, but perhaps you could quantify what you mean by "do machine learning"...what sort of business deliverable would you contribute?
Overall though, you might want to just aggressively hunt for the person's email and pitch in private :)
In 2013, the few bootcamps that existed and the fewer cohorts they each had were much more selective and they were producing in total many fewer candidates. The result is that bootcamp grads were very high quality (albeit very junior) and they got snapped up quickly.
In 2017 there are bootcampers everywhere flooding the market.
So I'm not sure they are outright lying but maybe they are using data to market their programs that is out of date.
All the bootcamp would have to do is be similarly very selective and do the same exact curriculum, and the people who "survive" these two weed-out courses (you needed to score higher than half your classmates in each course to receive a passing grade, otherwise you had to keep re-taking it) would be the ones able to get hired with nearly 100% placement.
Was this actually the rule dictated by the professor/curriculum or just a rule of thumb?
If you are choosing between fields or are looking to increase your income, how many people got good-paying, permanent jobs is highly important. It is also important if you are spending money that might be better invested in something else (such as a reliable vehicle or a down payment on a house if you live in the Midwest).
If you simply want the learning, the money isn't an issue ,and/or you don't actually care to land a job with the knowledge, then the job thing isn't an issue. All depends on perspective and desired outcomes.
Then with that under her belt, sign up for the boot camp. The advantages of this approach are:
- she'll find out if this is something she really wants to do before plunking down thousands of dollars
- with a bit of background knowledge, she'll be better able to absorb what's being taught at the bootcamp
- she'll have a better idea of what she wants to specialize in and can select the right boot camp for her
Finally, pay attention to open source. Not a lot of professions do their work out in the open like that, so take the opportunity to see how the sausage is made! Find the open source projects that these communities contribute to, and watch them do it. Follow the discussions on mailing lists, Github issues and pull requests. Look at the code and try to understand the criticism arguments. Ask questions. People are shockingly willing to help newbies who are trying to understand.
The bottom line is, there is real value in getting an expert to teach her how to code, but the more work she puts in herself, before, during and after the bootcamp the more she'll get out of it. If she's looking to pay $15K and get a high-paying job in exchange, she'll just waste the money.
Key things are:
- you get out what you put in. attending a boot camp is not a guarantee you'll land well-paying job. you have to demonstrate to a new employer you've mastered the skills to help their company
- depending on the bootcamp, it will take 8-10 hours a day. your social life aside from the days off will be shot. and the days off are spent doing laundry and playing catch-up on life
- don't neglect your fitness. since you're inside 8-10 hours a day, go to a gym and sweat for balance. otherwise you might suffer from burnout
- save up for at least 3 months of joblessness after the bootcamp while you look for work
- ask the bootcamp if they do interview prep. while it's cheating the system in some ways, it's extremely helpful for people who haven't been through the interview process. if you don't think well on your feet, or suffer test anxiety, this may be an issue
- lastly, if she hasn't done any programming at all, it'd be prudent to sign up for a local junior college course, or udemy to see if she actually likes doing it. i have a friend who talks all day about joining a coding school, took a python course, and realized it's not for him. it's better than accumulating more educational debt
https://learnpythonthehardway.org/book/
Best case it'll take less than a month (2 exercises per day, 52 exercises), is basically free, and if she's happy with everything at the end of it, she'll be FAR more prepared to jump feet-first into a dev bootcamp.
I compare learning to program to learning a language. 99hrs of having French slapped across your face won't make you a native French speaker, it's a long road to proficiency and mastery. Neither will 99hrs of Programming make you a native "Programmer".
However I'd pick someone who went through that 99hr drill over most people who hadn't even started.
but do you want to confuse her with python2 vs python3? When python2 should be out of the question, even if it's default on macOS. Though to be fair the difference should be learned, but it shouldn't be promoted to learn python2 for beginners. It will just confuse them. Even though many years have passed, but I think soon many libraries and frameworks will not support python2 at all (e.g. Django's next version will not), any new code I write - I write it in python3 and never think about python2.
The LPTHW is built for beginners in a sense, that it's easy to read and follow, though author is extremely __butthurt__[0] against python3 [1]. I guess it's the authors _shtick_ to be extremely opinionated, to a degree of incoherent blabber [1].
[0] sorry for my language
[1] https://learnpythonthehardway.org/book/nopython3.html
P.S. Though "Appendix A: Command Line Crash Course"[2] is probably one of the best promotions and intros into CLI .. and that is very useful to learn, instead of locking yourself as a beginner into some IDE.
Before in examples there were stuff like this:
$ python -V
Python 2.5.xThere is nothing in CS that you can't learn on your own and/or on the job. You do not need a school to teach you. Having said that, you need to want to learn this stuff and it is a long road. Decades after I graduated, I'm still learning new things (especially math -- since I sucked at it in school). So my first piece of advice: Realise that after a boot camp you will not know enough, nor have enough experience to really be qualified to do the job. Anybody who picks you up is taking a chance that you will grow into the job. Attitude is by far your biggest selling point.
If you go in with a hunger for learning and infectious enthusiasm, you will be a benefit to your team, even while being under qualified. If you go in thinking, "I don't really know if I want to do this, but it seems like an easy job that pays well", just stop now. I really can't stress that enough. Don't pay thousands of dollars to go to a boot camp to see if you want to do this stuff. Like I said, you can boot your own camp trivially. Computer + Internet + passion for learning will get you there. A good boot camp can really help you focus and point you to efficient ways of learning, but it can't give you the drive you need to succeed. My second piece of advice is to experiment first.
Finally, all of the people we have hired from bootcamps have had experience in other industries. Let me put it bluntly: They know how to show up to work every day and put in a full day's work. They know how to show up to meetings on time and pay attention. They know how to deal with difficult political situations. They know how to avoid being hung over on a weekday. Finally, they have experience being in a job that they hate and they have spent considerable amount of time and effort understanding what they want from a career.
My final advice: Don't graduate from school and go straight to a boot camp, unless you know for sure that you missed the boat and are desperate to be a programmer. Get some experience in the job world. Save some money. Think critically about what you want from your career. Then if you still want to make the jump, go ahead. Like I said, computers and the internet are everywhere these days, so it's not going to stop you from learning on your own.
I completed an online coding bootcamp about 5 years ago and got a job almost immediately afterwards. I've since become a Lead Dev for a local SaaS company, a mentor at that same school I graduated from, and a part time curriculum contributor.
This level of skepticism towards coding bootcamps is fair. I've seen some horror stories. But here is the thing: All failures involving more than 2 parties are usually the fault of both parties. Here is what I mean:
I'm currently mentoring about 5 students. Out of those 5, 4 are doing incredibly well. They are picking up the concepts, putting them into practice, and showing true growth. 1 of them is struggling hard. What is the difference? Well, in my opinion the difference is motivation. The 1 that is struggling did well his first few months, but when it got hard, he just wanted to start applying for jobs with what little he had learned. He didn't want to put in the work to finish his education. He was solely focused on the $$$ and not the thrill of solving problems with code.
So how could she decide if she will actually enjoy learning to code vs become someone that is only excited b/c of the money? Easy - try the free/cheap stuff first:
1. Codecademy.com 2. Codeschool.com 3. Lynda.com 4. Learn_____TheHardWay.com
The list goes on for a while. Tell her to sign up for one or two of the courses here and build something from start to finish. Nothing major. A todo list webapp, simple blog, or the like will do.
Then ask here: "Can you see yourself doing this 8 hours per day/5 days per week? If she can give you an honest 'yes', then offer her all the support you can give. If she hesitates, have her do more of the cheap/free stuff till it is clear. If it is a no, then it is a no.
Hope this helps. Sorry for the wall of text.
Has she ever tried coding, and if so does she see herself enjoying it as something she'd be doing several hours a day?
What is her reason for an interest in programming? Is it an interest in tech, solving big problems with tech, money, something else?
Would she be OK knowing that the job search for a bootcamp grad with no prior coding experience may be rather challenging (many grads go to work for the bootcamp itself, which is mutually beneficial as it boost placement stats while also giving the grad a job)?
How is her financial situation? Can she absorb a hit?
Is she incredibly bright and dedicated to the point of potentially being able to enter the field based on n months of self-directed education for free (MOOCs, online tutorials, videos, books, etc)?
The question is a bit more complex than it seems.
It's important to note that coding bootcamps are not created remotely equally -- some have stringent application requirements, whereas many are essentially scams / chop shops. I strongly caution against the latter.
In particular, at least one bootcamp that I know of only charges tuition after you get a job as a software engineer, and charges a % of your first year's salary. It's a really great way to align incentives between the bootcamp, students, and employers and I'm a particular fan of this program.
IMO these bootcamps are producing a basically undifferentiated product curriculum-wise (which, by the way can be learned via self-teaching on the internet). Only a few have real brand recognition. Drive, curiosity, raw horsepower, etc are a lot more important.
For specific pointers: your cousin should speak to as many recent alumni of various programs as she can to ensure that she has a legit program on her hands. Speaking with hiring managers is a good bet as well; "I've never heard of that place" is bad; "That place is a scam" is worse. She should also ask what the pass/fail rate is for students in the program. High graduation rate + upfront payment is arguably bad (shows they're incentivized to just get you out the door).
Best of luck!
I can't speak for how bootcamps are now, or the state in which DBC exists in 2017, but I can say that my cohort(s) were made up of lots of men and women and people ranging from border-line genius level to those with no programming experience. Those who came out and landed careers were the same individuals who had the drive and the passion, plain & simple. A person looking to be handed knowledge on a silver platter, eventually leading to a golden key to land a job, will be sadly mistaken no matter what kind of school they go to.
As others have said, it would be good for her to start learning to program on her own so she can see if she actually has any interest. It will sound cruel for me to say this but, if she hasn't already taken the initiative herself, the chances are low that she's cut out for it. Note that what I said just now is strictly my opinion. It certainly doesn't mean it's too late for her to begin now, but the drive is super important. This is coming from someone who went into a field knowing very little about it but expecting that passing the courses was going to land them a high-paying job. I switched to programming because I was forced to look in my heart and decide whether or not I was going to struggle to bestow bad art on to the world(as if there isn't too much already) for some short-lived glory. Plus I was already programming and already had the drive; I just needed reality and some good people to give me a good kick in the right direction for me.
Determining the legitimacy of a boot camp is difficult. I don't know that you really can. But what I got out of my boot camp was not so much an education but the space and the resources to accelerate my process into taking a full dive into web development, Agile, etc. On a technical level, there's almost nothing that a boot camp does that you can't get out of an online course. Heck, you could form your own "boot camp" with a Meetup group and spend maybe 1/100 the amount you'd spend on a boot camp tuition. A person has to go into a boot camp expecting a space, resources, and some leadership, rather than a concrete curriculum. At the end of the day, you can work for a company and not even include your education on your resume so long as the work that you have done stands out.
So your mileage might vary. I'm deeply skeptical of anyone from a bootcamp, to be honest. I think if you can really learn something and get your foot int the door with a small startup, then it opens the doors, but it's also hard without signficant amount of dedication.
I am not a day to day js framework/backend guy.
From the comments so far, I think there's some confusion about what you mean by this.
Are you trying to dissuade her? Motivate her? You're neutral, but asking for suggestions of things she might do to satiate coding desires other than a 'boot camp'?
Not saying all or even most coding boot camps are like that, but based on my reading of HN submissions, some definitely do overpromise and underdeliver.
Finding potentially more fitting ways of getting into the field could simply be helping out.
Related: https://www.wired.com/2017/02/programming-is-the-new-blue-co...
The ones who got good jobs were good applicants. They would have gotten the Dev job anyway. The ones who weren't strong got swept under the rug.
Your cousin might do better taking a year of CS classes and working on outside projects
Even checking out some of the "Intro to Programming" MOOCs from better institutions, it was pretty obvious to me that I'd have been utterly overwhelmed going into any of these cold as a student. If even a text editor or a command line is a new experience, there's just too much foundational knowledge/experience that has to be gained to move forward with what you're actually supposed to be learning.
(I know there have been efforts at places like CMU to teach intro courses that are actually real intro courses.)
The only reason not to go through a bootcamp, presuming it is reputable, is price sensitivity. They offer better value than a college degree (salary offer wise, both for technical and non-technical roles in tech industry), accelerate the pace of early-stage learning, and create healthy habits that are distinct to programming (e.g. tests, debugging, pseudo-code).
Long list of positive reasons here, as long as mindset going in isn't "I'm going to be a developer in 9 weeks" (true only on the loosest definition of the word).
http://signaltower.co/jennifer-dewalt/
She built one project each day for 180 days learning a bit more each day. She chronicled her mistakes and successes. HN had a post on it at the time and the majority of developers that responded were very supportive.
Much like colleges the rigor varies a lot BUT unlike colleges you're class will have a massive impact on your educatoion.
I studied a lot before I went in, it is highly recommended. Some other students struggled because they did not do much prep. Some students were annoyingly inquisitive and volunteered off-topic stuff frequently, eating into class time.
Have a capstone project or goal in mind when going in and try to do some pared down version for a final project(nearly all I have researched have several projects).
If you (op) can, help her get familiar w/ a dev environment. Explain things in depth and assume little. I was learning the absolute basics and someone introduced me to git, rails, terminal, scaffolding and ruby over a 10min convo. Obviously, it is great to dive in, but finding out what is important and how things work is important. Show her text editors, basic command line, git ect. Resources like hacker news, stack overflow, and maybe shell into an AWS instance.
I think they can be great, but they require a lot of prep, and a lot of research
This is a much better idea than dumping money into a bootcamp.
support hartl :)
Well, I might start at the $10-$15k price tag.
As others have pointed out, there are other ways to learn the material, but it may be that the 'career day' activities, etc. are worth the price of tuition.
For £10 you can't really complain whatever the outcome IMHO.
You should be complaining! Especially given the rest of your story.
This kind of thing is such bull shit.
Before you down-vote me: a man passed and now works at Trader Joe's; a woman failed and got a software engineering role.
Reverse those genders, and if you're outraged, have a think about whether you should still be down-voting me.
https://news.ycombinator.com/newsguidelines.html
We detached this subthread from https://news.ycombinator.com/item?id=13741232 and marked it off-topic.
I understand your decision. Respectfully, though, I think this sub-thread about the relative prospects candidates (and how it relates to culture more generally) is on-topic for the discussion here on considering enrolment in coding 'boot camps'.
As always however, your call. :)
The problem is with the one who failed the class. What do we know about her? We know that she either was too lazy to pass the class--implying she doesn't hustle--or she is simply unable to pass the class, implying she isn't qualified.
Combine this with the current political climate, in which a company looks like its trying to solve problems if it employs more women; and the fact that women joining male-dominated fields tends to cause a reduction in wages in those fields, and the fact that this seemingly unqualified and/or non-hustling woman was hired while many men were not, and its suggestive of a gender bias.
That is not to say the other women who were hired aren't qualified or don't deserve those jobs. Merely that there may exist a gender bias which is problematic in that it is focusing a particular outcome (equality of gender) at the expense of economic sense and efficiency; not to mention the personal expense of the qualified men and also at the expense of the unqualified woman who, if such a bias exists, is really being exploited.
Doubt that explains it.
I went through a large software development course, about 70 people. 60-40 male-female. Was a positive experience. The women all landed jobs instantly. As in, the day the camp ended, they all had jobs. The men, mostly, did not. It took months and multiple interviews for the men to get hired.
The demand for female developers is higher than the demand for male developers. (not that the demand for male developers is low). This doesn't particularly bother me, but it does appear to be a thing.
The way I look at it, most of the personal attributes that get you an entry-level job will end up having nothing to do with how well you will perform in that job. Gender is just another one of those.
No amount of hustle puts a candidate that failed a 'boot camp' above one that passed in a merit-based evaluation.
I promise, there wasn't any sexism involved.
1. They are self selecting to jump into the known gender gap in engineering.
2. Perhaps due to 1, they generally came from STEM backgrounds in great universities (Stanford, Michigan, UCLA, etc).
3. They had better final project presentations and projects than average. Perhaps due to 1 and 2.
If they were driven, had a previous math/EE/mech E degree from a top university, and a great GitHub project why wouldn't you hire them?
The woman in the example given in this thread failed; so certainly wasn't 'previous...degree from a top university' calibre.
To be absolutely clear, I'm not in anyway 'against success' for any woman. The sort of merit-based hiring you described is exactly what everyone should be doing.
But if candidate A is better than candidate B: hire candidate A! Whatever their gender, or fit for whatever other quota; scrap the damn quotas and targets.
The only targets should be relevant capabilities, traded off against cost of course.
> Before you down-vote me: a man passed and now works at Trader Joe's; a woman failed and got a software engineering role.
There's no reason to be outraged by a single anecdote. There are dozens or even hundreds of factors that qualify a person for a job beyond both their raw coding skill and gender.
If someone is taking a job at Trader Joe's because they can't find a programming job, there's a good chance there's a reason for that.
But you bring up a good point.
Kind of infuriating given both her parents are practising physicians and her whole education was completely paid for, unlike most people who have student debt staring them in the eye.
I'm young enough that the world I see being prepared for those not that much younger than me is, I think, going to be completely reversed from the motivation for the change.
I've tried to sign up for (technical) events and talks at my university because they sounded interesting, only to be told 'this is a women-only event'.
It would never even occur to me to hold a 'men-only talk on the latest foobar technique'; I suspect if I did, and refused to change my access policy, I'd be widely disparaged and perhaps kicked out!
Equality - fine. Positive discrimination is just discrimination, and at some point it will be 'traditional, negative' discrimination.
It's like the equality v equity cartoon - only the smaller box doesn't exist, and the middle-size child isn't short enough to qualify for a box: http://interactioninstitute.org/illustrating-equality-vs-equ...
That's not even it. Not only is it a sample size of 1, you are responding to a situation you know nothing about. Why did she fail? You have no idea, because it's not even your own anecdote. The fact that you're willing to jump in with "that is such bullshit" without even having the barest picture of the situation shows that your response is 1% motivated by the anecdote and 99% from your own biases and emotions about the issue.
In other words, your response says more about you than about the story.
Don't think it's fair? Interesting feeling, eh. Not very nice, eh. Be glad you haven't suffered it for literally your entire life.
Modern feminism increasingly seems to be an ideology based on the idea that women are always victims.
You've just described positive discrimination, and implied that you think it's a good thing.
Then you imply that you think women suffer unfairness for "literally your entire life". Which is it? You've either been a victim your entire life or you've benefitted from positive discrimination, in which case you probably need to stop acting like a victim.
The idea of giving someone an unfair advantage because someone like them possibly had an unfair disadvantage is ludicrous.
Based on your logic, in a generation from now we're going to have to start positively discriminating in favour of men, to make up for the fact that men are currently being discriminated against.
If it should be corrected, what specifically (i.e., what implementation) would you propose to do so? This whole issue is so contentious that I find people don't get much further beyond the surface disagreements.
At least in my country, all of the ways that females can be discriminated against in the workforce that are usually brought up are illegal.
(Pay gaps for the same work, promotions, sexual harassment, etc)
Yet people still complain they are problems. At this point, the onus is not on the rest of society to continue to try and make things easier for literally more than half the population. The onus is on the people being discriminated against to actually stand up for themselves and aggressively puruse legal action if they are the victims they claim to be.
For me personally, I find it quite ridiculous to hear people talking about all the gender stereotypes that exist today (and the discrimination that comes alongside them) and how we need action action action to solve them as if they are still problems.
My dad cooked more than my mum. I was picked on by girls at school. The girls always were told it's fine if they wanted to play a sport more dominated by guys, but god forbid a guy try to play sport with the girls. Rather than being discriminated against, the girls I know who went into software got given hugely preferential treatment over the guys and are routinely given better opportunities.
In everyone's effort to undo gender discrimination, they've forgotten that the aim is not to swing the pendulum to the other side, but instead to bring it back to the middle and treat people on their own individual merits.
For the sake of comparison, what country are you referring to?
https://www.humanrights.gov.au/our-work/sex-discrimination/p...
On whether structural discrimination exists, the question feels like a trap (even if not intentional) since we could probably spend hours arguing about what "structural" actually means.
But I'm going to go out on a limb and say that, in general, I don't think it does exist anymore, in the western world. Gender discrimination against women is now both socially taboo and illegal. And yet this perceived victimhood is increasingly used to justify very real (and openly practised) discrimination against men.
We're going to raise a generation of young men who are continually told how "privileged" they are, while feeling anything but privileged.
the question feels like a trap
Would you elaborate as to how you mean, in particular how I could have phrased it better? I sometimes struggle with how much qualification is necessary when posing questions like this: not enough and a question can come across as pointed, too much and it's just tedious. I'd like to strike the right balance.
One issue your answers do point out is that in this discussion you and 'jen729w are likely working from different premises: I doubt 'jen729w would be talking about positive discrimination if they didn't think there was some sort of discrimination occurring that needed correcting. Given that, disagreeing over solutions is likely inevitable, as you disagree there's discrimination that needs to be corrected for at all. I think it would be better to be upfront about that, so you can either figure out a common understanding you're working from (whether or not there's an issue with discrimination to be solved) before discussing any issues with potential solutions. For example, there's no reason not to ask 'jen729w what their understanding of the problem is. I think this kind of problem happens quite often when discussing contentious issues, which is unfortunate because I think it tends to make the issue worse rather than better.
Thanks again! I appreciate it.
I am. I'm young enough, though, that I'm acutely aware that the roles are going to be completely reversed for men not that much younger.
I've been unable to attend technical talks at my university that sounded interesting, because they're 'women-only'. There are exclusive events, clubs, networking for women - but of course there aren't equivalents for men! Disassociate yourself from the poor fool who dare suggest such a horrid thing!
I'm all for equality, but manifestly not for 'positive discrimination'. At some point, the tables will turn, and the generation of men below me will perhaps have this feeling of having 'suffered it for literally [their] entire life', and will want to positively discriminate back.
Or, we could just consider people on their merits, rather than their gender. Y'know, what women say they want?
Control theory-wise, perhaps it's demonstrably impossible to obtain the former without some measure of the latter, unfortunately.
A rational though process would be that this just adds to the sum of injustice in the world.
I'm perhaps presuming to much but with a name that begins with Jen which is often a short or familiar form of Jennifer I would have to wonder if you yourself are in favor of "positive discrimination" because you yourself have suffered from plain old discrimination the bad and in fact only form of discrimination there is.
I believe my life thus far has been tremendously more easy than a 40 year old black woman's would have been. Do you disagree?
Edit: here's a concrete example. I've basically been offered every job interview I've gone for. I'm good at my job, no doubt, but in some of those cases I'm pretty sure I wouldn't have been the strongest candidate.
But - forgive me if I sound like an asshole, I'm trying to make a point - I'm charming. I'm white, I smile, I dress well, and that makes me safe. I'm a safe option. Unsure who to hire? Hire that nice white guy.
This is the systemic, subliminal discrimination that positive discrimination is trying to address. I shouldn't be the default option just because I'm the white guy. I've had my time. Let's give the "hey we're not sure, so if in doubt hire the black lady" option a go. Fuck it, it can't hurt.
Now, I do absolutely disagree with PD where it favours a clearly inferior candidate just because of their race/gender/etc. That is clearly wrong, and gets people upset, and I see why and I agree.
It's a nuanced issue. But if you deny that there's an issue, or try to sweep it under the carpet, I believe you're being disingenuous at best.
The "funny" thing is that we are heading to a situation where the "positive" discrimination in favor of women will affect the weak side, the black/brown man, and they are not privilleged, of course. Now we have double negative discrimination.
BTH, if it wasn't so common for women to waste lot of hours everyday with cosmetic and aesthetic stuff, they would have more time to study computers and suffer less harassment. Win-win.
But people are upset because there is a PD that is favouring inferior candidate. In this case woman who failed. Of course a lot of assumptions, but still it looks like this.
Just focus in looking for candidates that are objectively competent at what they are supposed to do and fit in your culture. If you do it in an unbiased way then most groups should be represented.
Have you heard of the Equal Employment Opportunity commission? call them and tell them about your positive discrimination idea, they will surely like it... since you are in violation of EEO laws (sex discrimination = preferring females to males is as illegal as preferring males to females).
https://www.eeoc.gov/laws/types/sex.cfm
If you do, you will have a hard time proving that setting higher requirements for male employees is not unfavorable discrimination against them.
Your idea of a "make good" policy doesn't align with the laws nor does it make sense to punish people that have nothing to do with any prior discriminations made against the group you are advocating breaking the law for.
And yet, it's only seen as a problem if it's to favour the incumbent advantaged.
There's money in software development and women want it.
Note the lack of "positive discrimination" for jobs like coal mining, or any other profession on the top ten most dangerous jobs..?
You don't even have to go to the 'top ten most dangerous' - when did you last see a female plumber, electrician, gas technician, builder?
I was recently telling someone (female) that I was waiting in for an electrician. I said something like 'so when he comes', then said 'or she, sorry I don't know' - but then I realised actually, you know what I do know, the electrician is going to be a man and not because it's so hard to 'break into', but because women/feminists don't care about doing it.
Of course there are similar examples the other way around - male nurses or primary school teachers are examples to a lesser extent.
It's not really a problem, but we should at least be honest about what we mean.