zlacker

But isn’t it also important to appropriately identify and address the most disenfranchised group when we want to talk about how to help systemic violations of human rights? I mean, if I was debugging something and ignored the segfault because it only happened in one piece of the code, and I only solve bugs that apply to the entire codebase, I’d be a shit engineer

>>TeaDru+(OP)
> isn’t it also important to appropriately identify and address the most disenfranchised group when we want to talk about how to help systemic violations of human rights?

Back in the 1960s, yes, that was a reasonable approach, and we took it. In your coding analogy, we believed there was a specific bug and started applying patches to address it.

But we've been doing that for more than half a century now and it hasn't helped. So now maybe we should consider whether the actual bug might be something else, requiring different patches to fix.

>>pdonis+ql
I think you have both generic problems and module specific problems.

>>pdonis+ql
Arguably, no we haven’t been doing that for more than half a century now. There was a backlash after the initial push in the 1970s that clawed back a lot of gains and several places (Eg New York City) are still highly segregated in its schooling (and gotten more segregated over time).

>>TeaDru+Md1
> There was a backlash after the initial push in the 1970s

That doesn't mean we haven't been trying to fix racism for more than half a century. It just means the "fix" hasn't been working.

>>pdonis+ev1
Fixing racism hasn’t garnered significant traction with significant capital support for a while. Additionally, I would argue that attempting a 50 fix for systems that are multiple centuries old (and have had that much time to work their way into every part of society) seems short sighted.