Then came three enormous waves of academic and scientific talent to the US.
I don't think people have quite internalized *how* the US became the global leader in science and technology. It's partially a story of massive global talent migration.
And it's important to get this story right if we want to maintain
Then came three enormous waves of academic and scientific talent to the US.
In a massive own-goal, 1930s Nazi Germany dismissed ~15% of the physicists who made up a stunning 64% (!) of their physics citations.

With the Cold War looming, the US brought over ~1,600 scientists through Operation Paperclip and the Soviets ~2,500 through Operation Osoaviakhim.

Perhaps an underrated element in the fall of the Soviet Union is how we absorbed most of their top scientific talent as faith in the regime was starting to falter.
— Caleb Watney (@calebwatney) July 6, 2020
A great 1990 NYT article on it here:https://t.co/NXBldbgoV0 pic.twitter.com/TEgytTYsJv
https://t.co/i0QMZeQaEa
Using the Nobel Prize in Physics as a rough proxy, American scientists were involved in only three of the thirty prizes awarded between 1901 to 1933.
And a huge share of these Nobel laureates have been either first- or second-generation immigrants from these three waves.
We were unquestionably the best location for scientific research and so most inventors/promising academics wanted to come here.

1) US immigration restrictions are growing more burdensome
2) There are better opportunities to contribute to cutting-edge research at home
https://t.co/EYSUhofYeO
Today we grudgingly let the most talented individuals apply to live here; we do not actively recruit them.
The main job of immigration agents seems to be “avoid letting in terrorists” rather than “maximize the growth potential of the United States.”

We are the R&D lab for the world and we should act like it.
https://t.co/jwGI6exill
More from Tech
A common misunderstanding about Agile and “Big Design Up Front”:
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
I\u2019d recommend that the devs participate directly in the research.
— Jared Spool (@jmspool) November 18, 2018
If the devs go into the first sprint with a thorough understanding of the user\u2019s problems, they are far more likely to solve it well.
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.