I would. If you're building a stock trading app, why on earth shouldn't you hire at least one or two people on your design/development team that actually trade stocks and have experience with the current market?
It's not even a question of social diversity; it's just that you'll catch so many problems if you do - I can't count the number of times at my last job we ran into technical decisions about performance and algorithms where we didn't know what the right decision was because our dev team wasn't familiar with how the software would be used.
You can't user-test architecture, at least not without very long, very costly development cycles and refactors. It's valuable to be able to catch problems early. Even at a purely technical level, having a dev team that's unfamiliar with what you're building is a recipe for disaster.
Don’t you think that having women on the development teams might have helped catch the fact that voice recognition software didn’t recognize female voices before the software ever made it to QA, rather than after release?
On female voices not being recognized i'd like you to show me the article that tell this story, because it seems so obvious that i'm having a hard time believing it ( looks like something as obvious as understanding people speaking with different accents).
If i were a team leader honestly i wouldn't care about gender first. I'd be more interested in recruiting people from different weights, sizes, ages, maybe even races, and medical backgrounds first. And then, maybe gender would come into play.
For some problems gender is an important factor, for others it's not. The fact that this "gender" predicate divides the world into two half doesn't make it relevant per say. I could divide between blue eyes and brown eyes, or skin tan, or lactose tolerant, etc, and come up with fairmy big chunks.
Now I do agree that differences between men and women are indeed so important that it's an very interesting criteria in many topics. Although for some reason i don't think that's the argument you want to base your reasoning upon.
https://makingnoiseandhearingthings.com/2016/07/12/googles-s...
AI/ML inherits the bias from it's trainers - this is pretty well accepted.
It also fails to address the underlying problem that there are simply nowhere near an equal number of available female engineers as male engineers. Shooting for a goal of 50:50 ratio when that is not anywhere close to the ratio of the available candidates makes it mathematically impossible to not make other sacrifices...for what objective?
Your claim is that there are things that female engineers bring to the table that male engineers do not. My claim is that there is nothing a male engineer can do on the basis of their gender that a female cannot, and the inverse is equally true. In fact, I can't imagine a more offensive argument than saying "we need more female engineers so that our app is better at handling women's periods."
Airbags, for example: If breasts tend to get in the way, then the airbags aren't going to be as helpful for women or, alternatively, cause more harm to women simply because of breasts (I'm speculating the example, I don't know it to be true).
I would instead blame it on the people specifying the product features for not knowing their market ( and that usually is someone like a product owner).
Note that i clearly agree that having more people inside the company actually representing the target audience is a plus, but that's just a general rule, it doesn't apply specifically to having more women in tech team ( which i think is a nice idea, if only because tech is an interesting field to work in and women shouldn't miss this opportunity)