3 ms·
I think this comes down to what you think biases are and what you think should be optimised. Consider the gender imbalance in tech jobs. Let's say that is beca
by maest 6y ago
I think this comes down to what you think biases are and what you think should be optimised.
Consider the gender imbalance in tech jobs. Let's say that is because more men pursue tech degrees than women and this is because the field is already male dominated and women don't have female role models.
A hiring algorithm will optimise for the best candidate for the job. If we assume men are as good as women, the gender ratio will be skewed simply because the underlying population has a skew. However, we, as a society, may want to overweight women candidates even at a cost of choosing a slightly less fitting candidate because, in the long term, this will provide female role models and convince more women to join tech (there are reasons why this may be desirable, but it does have to be argued for).
Under this view, the algorithm is biased because it's optimising for the wrong thing - it is assigning no extra value to choosing a female candidate even if we, as a society, think there is value.
This is a thorny issue, though, as I've made some assumptions above and plenty of people will disagree with them, on various grounds. Still, I think this is a useful way if thinking about biases.
Also, viewed like a problem of figuring out the correct function to optimise, this suggests fixing this problem via slow and heavy handed law making (e.g. a blanket rule enforcing hiring gender ratios) is probably the wrong way to do this.
By the way, hiring committees can also be thought of as algorithms and at least part of their biases can be explained when viewed as them optimising for the wrong thing.
- glial 6y agoThis was a very clear way of putting it, thank you. Maybe it’s just me, but I find much of the discussion about algorithmic bias a bit fuzzy. Replacing “this algorithm is biased” with “this algorithm isn’t really optimizing what we intended it to” seems like a good step, with the added benefit that it requires people to be explicit about their objective function.
- Proven 6y ago> Replacing “this algorithm is biased” with “this algorithm isn’t really optimizing what we intended it to” seems like a good step, Why not simply: "we are biased" (that is, busybodies complaining about bias). From GP: > This is a thorny issue, though, as I've made some assumptions above and plenty of people will disagree with them, on various grounds. It's not a thorny issue. No one has to listen to algos. If your algo is buggy and suggests to kill rather than hire a candidate, would you? Secondly, how is anyone's business what kind of algos I run in course of operating a privately owned company? The thorny issue is how did we get to this situation where property rights have become so weak that busybodies of all sorts feel entitled enough to order others how they ought to use their property (that is, data and algos).