Now that India has flooded the world with FFMGs (Fake Foreign Medical Grads) we must rely on other means to exclude impostor doctors.
The US has two main defenses against impostors:
1. US doctors must complete a supervised US residency. Unfortunately, this residency requirement has been eliminated in 19 states, including mine.
2. Our second and final safeguard is the licensing exam. Almost all US doctors must eventually pass the three parts of the USMLE (US Medical Licensing Exam.)
Unfortunately, exam fraud is as simple as hiring a ringer to take the test for you (he needs to look vaguely like the picture on your driver's license) and avoiding the test centers that check fingerprints. (Grok summary attached.)
Or, impostors could obtain the questions in advance, from insiders or from earlier test takers.
If this sounds like a conspiracy theory, well, it already happened, and you will never guess where.
In 2024, hundreds of scores were invalidated due to leaked questions in Nepal (an Indian suburb) and to anomalous high scores at international centers in India, Pakistan, Nepal, and Jordan.
The statistically-unlikely scores were eventually blamed on early exam takers sharing the questions in WhatsApp groups.
In other news, you can take the first 2 parts of the US medical licensing exam in India. Then you can start practicing medicine in the USA.
Your Indian doctor might be a resident who purchased his Indian medical diploma then purchased the US licensing exam questions and took the test in India.
Fortunately, Part 3 of the exam, which must be passed at some point during residency, can only be taken inside the USA. So we can breathe easy, right?
Well, not exactly.
The US medical licensing exam is written and scored by two organizations. The first is the FSMB (Federation of State Medical Boards) whose president and CEO is....
wait for it....
Dr. Humayun Chaudhry.
The other organization that writes and scores the US medical licensing exam is the NBME (National Board of Medical Examiners.) NBME's Chairman of the Board is....
wait for it...
Dr. Reena Karani. That's her picture below, and why yes, she does happen to be Indian.
The physical testing centers are managed by a company called Prometric, whose Chief Products and Technology officer is....
wait for it....
Jay Chakrapani
Are you seeing the problem with our safeguards against fake doctors?
https://t.co/C3Eh2btRss
The CEO of Microsoft (Satya Nadella, from India) just hired a new, unqualified VP of Xbox (Asha Sharma, whose family is from India), replacing a white guy (Phil Spencer).
Normally the ethnicity of a person in a role doesn't actually matter. Who cares what part of the world a person has ancestry from, as long as they do a good job... right?
But, in this case, it's worth pointing out a strange -- highly racist -- pattern within Microsoft.
That pattern is this:
Microsoft managers from India, disproportionately hire people also from India (even if those people are less qualified than other, non-Indian, candidates).
A pattern which is overtly racist and anti-meritocracy.
In the case of Asha Sharma, the new Xbox lead, this is glaringly obvious... as she has no experience, whatsoever, working in games. Zero. Not a drop of gaming. (Her longest tenures were at Instacart and working on Facebook messaging.)
Are we to believe that there were zero candidates available, to lead one of the largest gaming organizations in the world (Xbox), with significant experience working in the gaming industry? Not *one*?
That is extremely unlikely. In fact, I can say with absolute certainty that there are many managers and directors, already working within Microsoft, with extensive experience (decades) shipping successful games and gaming hardware.
And that's just the internal candidates.
Which means that Asha Sharma was likely hired for a reason other than her applicable work experience.
It is a reasonable assumption, based on Microsoft's established patterns, that she was hired because of her ethnicity.
Microsoft is one of the largest users of H1-B visas within the entire Tech industry -- with the vast majority of those H1-B's going to employees from India.
More workers from India, replacing non-Indian workers. Every Microsoft employee has seen this happen over the years.
A little personal anecdote:
Back in the late 1990's, I worked within a small team at Microsoft (only a dozen or so people). When I first joined, the team looked roughly like the surrounding area (Redmond, WA): Mostly white, with one Indian, and one Korean.
It was roughly proportional to the community.
The Indian man was then promoted to a management position. And, quickly, things changed.
In less than 1 year, the team was now predominantly Indian (with a few people of other Asian ancestry)... with only 3 White guys remaining.
Within a single year, the demographic ratio had flipped. It now no longer matched the city in which we worked.
Then things got weird.
The team moved to a new floor of the building, and every employee within the group was given their own, individual office.
Well. Every employee... except for the 3 White guys.
We were put, together, in the smallest office available. The size of a long, thin closet. In fact... I believe it was originally just a storage closet.
It was so cramped that, whenever the guy at the back of the "office" needed to leave the room... the other two guys had to get up and exit one at a time. Single file.
We called it "The Honky Closet".
All requests for the "Honkies" to move to space where we could fit was denied by non-Honky management (despite several offices remaining empty).
The purpose was clear. It was one, of many, attempts to get the remaining "White guys" to willingly quit. Which we all did within a matter of months.
And, yes, those roles we also replaced with "non-Honkies".
I applied to Raytheon. I have a chemical engineering degree.
Please connect me with this retard so I can remind him that I have, like many engineers, applied multiple times to his fuckass company last year and didn't hear anything ONCE.
In 1984, Ken Thompson modified the C compiler to secretly add a backdoor whenever it compiled the UNIX login program.
Then he deleted all traces of that code from the compiler itself.
Even recompiling from scratch couldn’t remove the backdoor.
It wasn’t an attack it was a demo.
A proof that you can’t truly trust code.
Only the person who built the compiler.
I just added Fil-C runtime support for the prctl(2) argument that sshd uses to enable its seccomp filter sandbox. It works great! Just had to change sshd's seccomp filter to allow sched_yield, since the Fil-C runtime uses it.
So, I now have a memory safe OpenSSH on Linux that also has zero security or functionality regression versus normal OpenSSH. Like normal OpenSSH, it gets constant time crypto from OpenSSL. Like normal OpenSSH, it gets a seccomp filter and does privsep. Unlike normal OpenSSH, it's memory safe!
"I repeat, we are NOT rewriting our backend in Rust"
"You will implement this new API endpoint in Javascript and you will enjoy it"
"For the last time, we are not looking to replace Docker with Nix anytime soon"
https://t.co/WkLrtpWgdK