News for hackers. Stuff that matters.
Re:Discrimination in the Age of Algorithms by raverbashing on Saturday March 02, 2019 @05:58PM (#19291647)
It's not so much about programming for social justice, but accounting for biases that are present in the current status quo and that end up in training data

There was a recent talk from a Meetup engineer about this but I can't find the link right now.

Re:Discrimination in the Age of Algorithms by danieltillett on Saturday March 02, 2019 @06:12PM (#19291713)
Then shouldn't the algorithms incorporate the unbiased data rather than incorporate something we know is biased to correct for other biases?

A question. How do we know the algorithm is biased if it give a racial disparate result? Don't tell me the evidence is that the result is racial disparate.

Re:Discrimination in the Age of Algorithms by raverbashing on Saturday March 02, 2019 @06:36PM (#19291803)
There usually isn't unbiased data (think: law enforcement databases), though you could maybe remove the variables more likely to be discriminated against and train on that

There are statistical analysis that can answer your second question, and it's not only based on disparate results (though that's probably part of it). And the solution is not "changing the signal" of the bias

Re:Discrimination in the Age of Algorithms by danieltillett on Saturday March 02, 2019 @07:55PM (#19292084)
If there are statistical analysis that can answer if the data is biased why isn't the focus of attention all biases rather than just biases that may result in racial discrimination?

Shouldn't all the arguments be over the data and any biases present (and how to obtain unbiased data) and not the result?