FalconInMS

Glen's an awesome guy, and I feel a little bad about using his comment as an example. I don't want anyone thinking I'm putting him on blast, because I'm really not. I'm just using something he said to illustrate a point. (Sorry, dude. Please don't hate me.) He said: "Considering I deal with Indians all day every day and not a single instance has it been a good experience..." All right. Let's take that argument to its logical extreme. Arguendo, let's assume every member of racial group X you've ever encountered has been absolutely horrible. Every single one. No exceptions. Here's the philosophical question I want you to consider: Are you making a rebuttable judgment about someone's behavior, or an irrebuttable judgment about their ancestry? That's an important distinction. Do you dislike members of group X because of what they do, or because of what they are? If you encountered someone from that group who shared your values, respected your culture, worked hard, behaved honorably, and treated you with dignity, would you welcome that person? Even if there was only ONE person like that out of 2 billion people? Or would you reject them anyway, simply because of their ancestry? Is there anything that individual could do to earn your respect? If the answer is yes, then your objection isn't fundamentally racial. You're objecting to conduct, values, or cultural practices. If the answer is no, then we're having an entirely different conversation. I'm not going to tell you which answer you have to give, but I think it's pretty obvious which one I'd hope you'd choose. Now, let's talk about India. This is actually very relevant to my professional life. One of my primary responsibilities involves bringing substantial amounts of technical work back to the United States, including work previously outsourced to India or performed by H-1B employees. And you know what? We've found that a majority of the work we've evaluated from those arrangements has been substandard. Notice my wording. I said that a majority of the work we've evaluated has been substandard. That's an observation about our actual experience, not a declaration about the innate abilities of 1.4 billion human beings. And here's something else that needs to be discussed, because it's been one of the biggest problems we've encountered. Fraud. Actual, deliberate, calculated fraud. We've discovered people misrepresenting their degrees, their professional experience, and their technical abilities. We've encountered a substantial contingent of people demanding kickbacks in exchange for helping friends and family get hired. We've discovered employees who weren't even doing their own jobs. They were quietly outsourcing their responsibilities to other people, sometimes through unauthorized VPNs and completely unapproved remote-access arrangements. Think about that last one for a moment. We're entrusting these people with access to corporate infrastructure and potentially sensitive customer information, and some of them are handing that access to people we haven't vetted, haven't authorized, and in some cases don't even know exist. That's a security nightmare. And this wasn't one or two isolated incidents. Across the workforce we've been examining, we've identified problems of this nature involving roughly a THIRD of the people working over there. One-third. Now, before someone deliberately misunderstands me, that's a figure from our own experience, with our own workforce. I'm not claiming that one-third of Indian workers everywhere are fraudulent. I'm also not going to pretend that what we've encountered is insignificant. We've found recurring patterns of misconduct, including practices that appear to have been tolerated, normalized, or simply ignored in the environments we were dealing with. And I'm going to be blunt about something else. A significant part of this failure was OUR fault. We allowed too much of the operation to manage itself. We didn't exercise sufficient oversight. We didn't adequately verify credentials, enforce access controls, or investigate suspicious arrangements. We trusted systems and management structures that, in retrospect, hadn't earned that trust. Perhaps most frustratingly, there were times when people were reluctant to confront obvious problems because they were afraid of being called racist. Well, I'm sorry, but that's absolutely ridiculous. Fraud is fraud. Lying about your qualifications is fraud. Demanding kickbacks for employment opportunities is corruption. Secretly subcontracting your job to an unauthorized third party is misconduct. Allowing unvetted individuals to access corporate systems through unauthorized VPNs is an unacceptable security risk. None of those things becomes acceptable because the person doing them belongs to a particular racial, ethnic, or national group. None of those things becomes racist to investigate simply because the people being investigated happen to belong to one. We have obligations to our customers. We have obligations to our employers. We have obligations to the people whose information we're entrusted to protect. Those obligations do not disappear because enforcing them might make somebody uncomfortable. So we've had to change how we operate. Better verification. Better oversight. Better accountability. Better security controlsLess blind trust in arrangements we cannot independently audit. And yes, a better understanding of the workplace practices and incentives that allowed these problems to flourish. I am perfectly willing to criticize cultural practices that enable corruption, nepotism, dishonesty, or the avoidance of accountability. I'm not willing to pretend that those practices are inherent characteristics of every Indian person. There's a difference. In fact, the honest, competent Indian employees who actually do their jobs are harmed by these practices, too. They have to work alongside people who undermine trust, damage reputations, and make everyone else's job harder. They deserve better. And that's precisely why we need to distinguish between the people who engage in misconduct and the people who don't. The answer to widespread fraud isn't racial discrimination. It's widespread accountability. Investigate the conduct. Verify the credentials. Audit the access. Enforce the standards. And when somebody violates those standards, hold them accountable. I don't care whether the person responsible is Indian, American, Black, White, or a three-headed Martian from the moons of Jupiter. You don't get to compromise our customers' security. Period. And here's the interesting part. We're keeping some of those overseas employees. Why? Because some of them are actually quite good at their jobs. Some are excellent. We've also learned that part of the problem wasn't necessarily the employees themselves. It was how the work was organized, communicated, delegated, and managed. Cultural differences, basically. We've been getting better at that, too. Let me give you an example. I've worked with Indian colleagues who are extraordinarily detail-oriented. Give them a narrowly defined technical problem, clear requirements, and something concrete to investigate, and some of these folks will find things that everyone else missed. I've had them save my ass more than once. I've also had them annoy the living hell out of me by obsessing over some microscopic detail that had absolutely no bearing on the larger problem we were trying to solve. Sometimes those are the SAME PEOPLE. That's where management, communication, and understanding individual strengths become important. A person who struggles with ambiguous requirements or big-picture architectural decisions might be absolutely fantastic at auditing configurations, identifying inconsistencies, validating data, or finding subtle implementation errors. That doesn't make them stupid. It means you need to understand what they're good at, where they need support, and how to use their talents effectively. Of course, there are also people who simply aren't very good at their jobs. Those people exist in India. They exist everywhere. I have no obligation to pretend otherwise. Then there's the language barrier. (Oh, good Lord, the language barrier.) Some of my colleagues speak excellent English. Others have accents so thick that I genuinely struggle to understand them in conversation. My autistic brain does NOT appreciate having to simultaneously decode unfamiliar pronunciation, follow a technical discussion, and figure out what someone is asking me to do. It's exhausting. So with certain colleagues, I prefer written communication. And guess what? That often solves the problem. Suddenly, someone I found incredibly frustrating to work with over the telephone becomes a perfectly productive colleague over text. Their technical knowledge didn't change. Their intelligence didn't change. Their ancestry certainly didn't change. We changed the way we communicated. And the result improved. Now, am I going to sit here and pretend there aren't cultural problems? Absolutely not. There are workplace practices and expectations I've encountered in offshore arrangements that I find deeply frustrating. An excessive reluctance to challenge authority. Telling a manager what they think the manager wants to hear instead of delivering bad news. Treating a checklist as more important than the actual objective. Being reluctant to admit that something isn't understood. Sometimes it's bad ehough they refuse to gengage with me because i'm a woman. I've encountered all of these. And when they happen, they're problems that need to be corrected. But here's the critical distinction: those are behaviors I've observed in particular workplaces and teams, not characteristics magically encoded into Indian DNA. Some people bring those habits with them. Some don't. Some adapt quickly when expectations are made clear. Some resist. And some of the people who adapt become genuinely valuable colleagues. I've also worked with people from India who admire American culture, appreciate our professional norms, and make a sincere effort to understand and adopt them. Why on Earth would I reject those people? Because they were born in the wrong country? Because their parents had the wrong ancestry? What exactly would that accomplish? And don't mistake any of this for an endorsement of our immigration system, H-1B abuse, or the outsourcing of American jobs. I have serious objections to all three. If it was up to me? I'd onshore all of it because I'd rather be giving Americans these jobs. It's not up to me, though, so I work within the framework i've een asked to. American companies should not be using foreign labor arrangements to undercut American workers, suppress wages, or avoid investing in domestic talent. But that's a criticism of corporate practices, government policy, and incentives. It is not a justification for treating every Indian person as an interchangeable representative of everything I dislike about those practices. Here's what I've learned from doing this professionally: It's a mixed bag. Some people are excellent. Some are mediocre. Some are terrible. Some cultural expectations create friction. Some individual strengths are genuinely valuable. Some problems can be fixed with better management. Others require replacing people or bringing the work home. You learn to recognize the differences. You learn what works. You stop making excuses for what doesn't. And most importantly, you judge the person standing in front of you instead of condemning them for the behavior of everyone who happens to share their ancestry. I don't believe in racial collective guilt. I don't believe in racial collective virtue, either. I believe in standards. I believe in accountability. And I believe that anyone, regardless of where they were born or what their ancestors looked like, should have the opportunity to meet those standards. If they do, I'll respect them. If they don't, I'll criticize them. Many times i'll hand them their walking papers. That's not lowering my standards. That's actually having standards.

Dude and I just said nice things about your other article. God damn it. Are you okay with a White Muslim imposing Sharia law on you and forcing you to pay jizya? Are you okay with a White communist confiscating your home or business and handing it over to his political friends? Are you okay with a White Democrat confiscating your firearms? Are you okay with a White criminal robbing you in the street? Are you okay with a white rapist defiling your wife? No? Then apparently being White isn't sufficient to make someone a desirable member of your society, is it? Now let's reverse the question. Would you rather have a Black neighbor who respects your property rights, your constitutional freedoms, your family, and your way of life, or a White neighbor who wants to take all of those things away? Because that's the distinction you seem utterly incapable of making. Race tells me absolutely nothing about whether someone shares values. Their beliefs, conduct, and character tell me quite a lot. You keep talking about the civilization White Americans helped build. Fine. Let's talk about what they built. A constitutional republic. A system of government founded on principles of individual liberty, property rights, religious freedom, and equality before the law. And your argument is that these principles should be subordinate to racial ancestry? What an extraordinary way to celebrate the accomplishments of your ancestors: by rejecting the very principles you claim make their civilization worth defending. I don't owe you gratitude for my constitutional rights. They aren't yours to dispense, and they aren't yours to revoke. I will stand beside a White man who defends my liberties. I will stand against a White man who threatens them. And I'll apply precisely the same standard to everyone else. I'm interested in preserving a civilization, not running a racial membership club. And if you cannot understand the difference, perhaps you should spend a little less time boasting about the civilization your ancestors built and a little more time studying what made it worth building.