Comment by joshuamorton | Hacker News Reader

Comment by joshuamorton | Hacker News Reader

Parent Full thread

But I'm not making it into a cartoon. You're suggestion is to take minorities and segregate them into specific majority-minority teams. Here's a definition of "ghetto" from a Google search:

> put in or restrict to an isolated or segregated area or group

That is absolutely what your proposal entails. Consider the outcomes of this proposal:

> I'm sorry, we don't have any $minority teams working on $area_of_expertise right now, so I don't see a good fit for you.

Note that now your minority group is explicitly a marker of what you can or cannot work on. Whether or not you intended it, your proposal creates a racially defined hierarchy, much in the same way that we already have stereotypes about "women work in frontend/ui roles", you'll only support those stereotypes and make them systematically ingrained. Further, without minority advocates and voices at the level of people picking the "minority" teams, minorities will be less likely to access those projects that are considered more interesting/challenging/prestigious.

And note that the more reasonable "make all teams minority majority" is not possible unless your population is also minority majority, and even then its artificial and perhaps too strict.

Please don't object to my calling a spade a spade. I've provided a reason that your suggestion is flawed, and instead of defending it on its merits, you've objected to my word choice.

> segregate them into specific majority-minority teams

Again, you mischaracterize what I said:

"I believe this can be done by hiring competent minorities into teams [2], where although they are a minority in general they will not be on their team. These teams should not only be that minority as you in a truly inclusive system can't define people by a trait."

Where I in the follow up comment say:

"... the teams are not entirely comprised of minorities and this team structure is supported by research that shows that it feels socially isolating to be the sole representative of your minority in your daily life. Maybe even a majority is not a minority on the team."

> put in or restrict to an isolated or segregated area or group. That is absolutely what your proposal entails.

Because of the preceding comments I disagree with this characterization. These teams are an acknowledgement that many find it hard to feel like they are the sole representative of their minority in their daily life.

It is a tool that should only be applied at discretion and when appropriate, and to make it work it needs support.

> Consider the outcomes of this proposal: I'm sorry, we don't have any $minority teams working on $area_of_expertise right now, so I don't see a good fit for you. Note that now your minority group is explicitly a marker of what you can or cannot work on.

> Whether or not you intended it, your proposal creates a racially defined hierarchy, ..

This was addressed in the proposal: "Since its a minority you probably have to do some extra legway in facilitating matching these teams well to problems the the team members find interesting and that there are growth opportunities. However, that is an ongoing conversation you should be having at any rate."

I never said it was easy and that we wouldn't have to have extra support to make this work. That support requires staffing, training, recruiting etc etc that spends extra effort to make this very difficult thing happen.

> Please don't object to my calling a spade a spade. I've provided a reason that your suggestion is flawed, and instead of defending it on its merits, you've objected to my word choice.

To my points above these are clearly mischaracterizing of what I am saying by at best not carefully reading the proposal. I am asking you for the same respect in this discourse that I am giving you, and I believe that is fair.

Edit: @joshuamorton I am sorry, I can't keep pointing to the same quotes showing how you interpret what I say is different from what I actually said with no progress in our discourse. I think we just have to agree to disagree.

>I can't keep pointing to the same quotes showing how you interpret what I say

Pointing to quotes cannot do this. You need to explain how what I'm saying is a mischaracterization. To be clear, your suggestion is

> hiring competent minorities into teams, where although they are a minority in general they will not be on their team.

My claim is that is that

(1). This means hire minorities solely into majority-minority teams.

(2). Hiring minorities solely into majority-minority teams is a form of segregation.

Just restating your original suggestion does not address either of these claims, you need to do something to show that (1) or (2) is false. I believe the reason that you have not done this, and have instead resorted to restating your original claims is because you are unable to reject either of these claims. Instead you are attempting to obfuscate this fact.

I'm familiar with the research about the harms of being a minority and the impact it can have on performance, but as far as my claims about segregation go, those arguments are irrelevant. And that's why I previously said that they were a distraction. If you want to show how my interpretation of your claims is false, you need to show that either claim (1) or (2) is false, and so far you have not done that, you've simply restated your thesis.

> I'm familiar with the research about the harms of being a minority and the impact it can have on performance, but as far as my claims about segregation go, those arguments are irrelevant.

I strongly disagree. You have to respect the human in the equation if you want to facilitate inclusion, and make sure that you do everything to facilitate the change you desire. Otherwise you risk filtering for people that check the right boxes that happen to be similar to the people already working there.

Research from 2007 to 2015 in [1] indicates that what we are currently doing is not working:

- The number of black women in the industry declined by 13%, the study found.

- There was also an increase in Latino executives, but the overall representation of Latinos declined from 5.2% to 4.8% and they still represent a very small fraction of corporate leaders.

[1] https://www.theguardian.com/technology/2017/oct/03/silicon-v...

> Hiring minorities solely into majority-minority teams is a form of segregation.

I never proposed solely recruiting minorities for these kind of teams. I said: "It is a tool that should only be applied at discretion and when appropriate, and to make it work it needs support."

Also, the definition of segregation is:

- the action or state of setting someone or something apart from other people or things or being set apart.

which does not appropriately describe a team that is mixed and where some members come from one or more minorities. Also, I would again like to point out that minorities can still choose to work on any team as this is a tool applied at discretion.

Of cause, as I stated you need to do extra work to make sure that minorities can choose opportunities freely and be supported appropriately after the choice is made.

The definition of ghetto is:

- a part of a city, especially a slum area, occupied by a minority group or groups.

Which for the same reasons does not properly describe the proposal.

Note: I think I've shown here that you've used historically loaded terms like segregation and ghetto inappropriately to describe parts of my proposal. This is a very dirty rhetorical trick when the proposal is intended to apply to minorities, and it is not appreciated.

You've cherrypicked definitions of segregation and ghetto. I'll repeat the original definition that dictionary.com provided:

> put in or restrict to an isolated or segregated area or group

And here's a merriam webster definition of segregation:

> the separation or isolation of a race, class, or ethnic group by enforced or voluntary residence in a restricted area

Does, or does your proposal not put or restrict minorities to certain projects and teams?

Does, or does your proposal not separate or isolate minorities into restricted teams?

As for your cherrypicked definitions:

>which does not appropriately describe a team that is mixed and where some members come from one or more minorities

It does if those minorities are prevented from accessing other teams (or even if it is just more difficult).

>Which for the same reasons does not properly describe the proposal.

Replace the word 'city' with 'company' and it absolutely does!

>I strongly disagree. You have to respect the human in the equation if you want to facilitate inclusion, and make sure that you do everything to facilitate the change you desire. Otherwise you risk filtering for people that check the right boxes that happen to be similar to the people already working there.

This is irrelevant to whether or not your proposal is essentially segregation. Like I'd previously said, this may make it segregation that you feel is scientifically backed, and morally better than what we are doing now, but that doesn't make it not a form of segregation. You appear to believe that if something is better than the system we have now, it cannot be segregation, and that view just doesn't make any sense at all.

>It is a tool that should only be applied at discretion and when appropriate, and to make it work it needs support.

This is a cop out. It basically can basically be rephrased as "we should only use segregation when it makes sense". If you want to make that argument, that's fine, but its still segregation.

I made some clearer objections in https://news.ycombinator.com/item?id=16092706, and you handwaved them away. In essence, when faced with objections to this proposal, your response has been either "I don't like your words" or "yes you have to be judicious and thoughtful when using this strategy", but that just handwaves any of the potential problems away behind magic "judicial and thoughtful"ness. Unless you can craft a strategy beyond the vague "judicious and thoughtful" one you've proposed that materially prevents this proposal from descending into a form of segregation and causing outcomes like the one I suggested previously and will repeat here:

> I'm sorry, we don't have any $minority teams working on $area_of_expertise right now, so I don't see a good fit for you.

I will continue to call your proposal exactly what it is: a strategy of segregating minorities into minority-majority teams in an effort to reduce some of the negative effects of being a minority.

Now to change gears a bit: note that I've never said that this strategy is morally wrong, only that it is a form segregation. You appear to resist that characterization, my goal here has been to show why there are flaws in alternative approaches to affirmative action, and why any such policy is going to be easy to characterize in an unpalatable way.

In other words, while I do personally disagree with your proposal, I was taking on a bit of a devil's advocate stance. In the same way that you find it very easy to attack affirmative action policies as a form of "reverse racism", its pretty easy to similarly attack your majority-minority team proposal as segregation. You seemed to take this very personally, and I apologize for that.

And to be clear, I actually think that a slightly less extreme, but similar proposal to yours is a good idea. Namely, softly enforcing teams with minorities having >1 minority to at least alleviate some of the minority threat you get. However this too is flawed, both from the perspective of it doesn't help minorities as much as some proposals, and because it can be easily characterized as a racial quota.

As an aside, there's another flaw in both of these proposals that isn't simply an issue of branding: they don't address the sourcing issue that affirmative action attempts to. Its very hard to have competent minority teams if you have difficulty sourcing competent minorities (and I should clarify that this is not because they can't or don't exist). A lot of the common AA policies try to reduce false negatives or do creative things to source more minority talent, and are still objected to for various reasons.

Edit: It also appears that you're downvoting my comments, since all of my comments deep in threads responding to you are at 0, and most of my others in these threads are positive. If that's not the case, do let me know, but it makes me uninterested in continuing this discussion with you.

Making a false statement over and over doesn’t make it any more correct. This is just ugly rhetoric which is why I stopped interacting.

As a liberal I think the left has a huge problem with this kind of narrow mindedness on what opinions one can hold and unwillingness to listen, using rhetoric to disingenuously twist someone’s viewpoint into something clearly offensive. It clearly doesn’t matter what you actually say.

The use of this kind of rhetoric seem to build upon the incorrect assumption that democracy is the default state, and that you can use this to enforce an us vs them so that it’s easier to fight a social justice war. Let’s hope the left doesn’t create an authoritarian state by systematically acting using authoritarian means.

This is not a constructive response, it appears to be a rant. I have no interest in continuing this discussion if you're responses will be unrelated to the content of my posts and instead be emotionally charged complaints that I'm treating you unfairly.

I think we both share that feeling. Best of luck working for what you believe in. I think we’ll work for different things. :)

To be clear: your first post described "Affirmative Action" as "bigotry, sexism, and racism". As I explained in my longer post, I was applying a similar description to your proposal.

If you're going to characterize "affirmative action" with such charged terms as "racism" "sexism" and "bigotry", do you at least see the irony in complaining when I do the same?

I'm willing to agree that your proposal is not intended to be segregation, are you willing to agree that affirmative action is not racist or sexist?

Nice play with the word intended. I can agree that affirmative action is not intended to be racist or sexist. It’s a tool, with positive and negative consequences. I am not saying it’s a tool that we should not use.

Unfortunately the number of Hispanic and African Americans in tech decreased between 2007 and 2015 while gender balance improved which is part of the reason why I think we need to look into other tools as well.

I think it’s worth asking oneself if our current tools are not inclusive to different viewpoints, and just filter for people that are similar to the ones already there and happen to check the right boxes.

Would someone that dresses, talks, and walks like they come from east Oakland be hired even if they were a capable engineer or have we not made ourself inclusive to that?

> It also appears that you're downvoting my comments, since all of my comments deep in threads responding to you are at 0, and most of my others in these threads are positive. If that's not the case, do let me know, but it makes me uninterested in continuing this discussion with you.

No, I actually do not have enough karma to downvote and even if I did I do not believe a participant in a discourse has the right to do that. It would be counterproductive for me to do so.

Alright. I meant no offense and was hoping this was the case, it just looked suspicious. :)

>Again, you mischaracterize what I said:

You have not explained how this is a mischaracterization. Your proposal was to place minorities into solely majority-minority teams, my claim is that this is a form of segregation. Which of those two claims is a mischaracterizaiton?

The rest of this post is just distraction that appears to claim that this is morally good segregation, or scientifically supported segregation, but its still segregation.

Reply on news.ycombinator.com