Yep. Google, at least, started this transition during Trump1.

The company has long had engineering sites in various other countries, but until Trump1, the primary focus was always on cities where Google thought the global talent would want to live. Low cost was clearly not the driving factor in the selection of London, Zurich, Munich, Tokyo and Sydney, to name a few of the ones I visited. US sites were similarly not located in low-rent areas. The workforce was definitely global, because Google wanted to hire the smartest people and while the US does have its share of brilliant minds, the US has only 4% of the world's population, so most teams -- even in the US -- ended up being minority American.

During COVID, Trump leveraged the health crisis to essentially halt H-1B approvals and renewals. This caused significant problems for Google. My own team lost a few people because they couldn't get their visas renewed and had to go back home. Some chose to move to other Google sites overseas where Google could get them a work visa, others simply went back to their home countries. One trans woman on my team was in a particularly tough spot because her home country (India) refused to renew her passport because it didn't recognize her new gender. She couldn't get her visa renewed, couldn't go home to India, and also couldn't move to any other country with an expired passport. Luckily, she had a lot of nVidia and Google stock she'd been saving up to buy a house, and by cashing that out had enough free cash to get an EB-5 "investor" visa. It's good to be rich, of course.

Anyway, Google saw what was going on and, anticipating future troubles of the sort, refocused its overseas office plans on building up teams and infrastructure, especially in India which provided so much of Google's engineering talent anyway, with the intention of shifting whole projects and workstreams there. The company had long required a significant percentage of all staffing growth to be in the US (and especially in the bay area), but that policy was scrapped and replaced by its opposite: A certain percentage of all new roles must be based overseas.

It's still the case that the center-of-mass of Google is in the bay area, but the company is actively working to change that, to build up overseas capacity, and not just groups of junior engineers under a manager whose role is to pass them detailed requirements for implementation, but instead full teams with highly-skilled and experienced senior engineers and managers able to take full ownership of major product areas and move them forward.

Trump's latest moves will just accelerate this transition. The result will eventually be a hollowing out of the company's US capacity, and therefore a reduction in the need to hire American engineers. Lucky for me, I'm leaving Google for a startup and anyway am not far from retirement. Between this stuff and AI being poised to replace junior engineering staff it's a good time to be getting out.

Also, I think it will soon be time to start shifting investments out of the US.

No. They probably don't want to hear the Roosters crowing in the background when employees are working from home on a Teams call and figure that since livestock isn't allowed in the office they can avoid that type of interruption.

And no. This isn't a joke. I've had at least three calls like this from Xerox Support over the past 5 years when their support site would crash and I had to call them for toner and parts support. To be fair I always got the parts and support on time so Kudos on Xerox but its definitely not something you expect to hear on a business support line.

Is NASA doing anything useful?

Aren't they just trying to repeat what SpaceX has already done?

I vote to call them the Sardaukar.

It holds up in some cases, not in others, and calculating an average muddles that.

Personally, I use AI coding assists for two purposes quite successfully: a) more intelligent auto-complete and b) writing a piece of code using a common, well understood algorithm (i.e. lots of sources the AI could learn from) in the specific programming language or setup that I need.

It turns out that it is much faster and almost as reliable to have the AI do that then finding a few examples on github and stackoverflow, checking which ones are actually decent, and translating them myself.

Anything more complex than that and it starts being a coin toss. Sometimes it works, sometimes it's a waste of time. So I've stopped doing that because coding it myself is faster and the result better than babysitting an AI.

And when you need to optimize for a specific parameter - speed, memory, etc. - you can just about forget AI.

Hey, industry, I've got an idea: If you need specific, recent, skills (especially in the framework-of-the-month class), how about you train people in them?

That used to be the norm. Companies would hire apprentices, train them in the exact skills needed, then at the end hire them as proper employees. These days, though, the training part is outsourced to the education system. And that's just dumb in so many ways.

Universities should not train the flavour of the moment. Because by the time people graduate, that may have already shifted elsewhere. Universities train the basics and the thinking needed to grow into nearby fields. Yes, thinking is a skill that can be trained.

Case in point: When I was in university, there was one short course on cybersecurity. And yet that's been my profession for over two decades now. There were zero courses on AI. And yet there are whitepapers on AI with me as a co-author. And of the seven programming languages I learnt in university, I haven't used even one of them ever professionally and only one privately (C, of course. You can never go wrong learning C. If you have a university diploma in computer science and they didn't teach you C, demand your money back). Ok, if you count SQL as a programming language, it's eight and I did use that professionally a few times. But I consider none of them a waste of time. Ok, Haskell maybe. The actual skill acquired was "programming", not a particular language.

Should universities teach about AI? Yes, I think so. Should they teach how to prompt engineer for ChatGPT 4? Totally not. That'll be obsolete before they even graduate.

So if your company needs people who have a specific AI-related skill (like prompt engineering) and know a specific AI tool or model - find them or train them. Don't demand that other people train them for you.

FFS, we complain about freeloaders everywhere, but the industry has become a cesspool of freeloaders these days.

The number of people isn't the problem here.

The "started every" is.

How did they not catch that during development and found a solution? I mean, the meme's where a TV ad starts Alexa and orders 10 large pizzas are a decade old now.

It's not just amazon.

I ordered a thermostat for my mustang last week. It was described as "sold and shipped by Walmart."

A couple of days later, I found an Autozone box on my porch. And not just the box, but the shipping return address was to auto zone!

??

the real tragedy of Viet Nam was that the US achieved *exactly* what it set out to do--which was a really stupid thing to do and waste lives upon.

The mission was *not* to defeat the north Vietnamese, but to keep them on their side of an imaginary line. US troops that went over the line got called back.

When the US finally decided it wanted to stop playing, the north wouldn't let them simply leave. To get them to talk, the US bombed them into submission, for crying out loud.

By any *military* standard, Viet nam was an overwhelming success for the US. US troops controlled whatever ground they chose, and won all of the battles.

But "resist aggression and stay on your side of the line" is a *stupid*, even criminal, thing to ask of a military. As is the lives it through away for idiocy.

Dish antennas can be used for both transmitting and receiving. The reciprocity theorem says they work equally well in either direction.

Nobody uses dye-sensitized solar cells. They were an interesting idea for a technology, but the improvements in silicon cell performance along with reductions in cost just made their mediocre performance obsolete.

Also, nobody uses plastic coatings for solar cells. Plastics simply deteriorate too fast. Everybody uses glass.

That depends on how much I'm paid.

For enough money, I can tolerate almost anything.

The truth is an absolute defense against libel in America.

It is a weaker defense in the UK.

Another difference is that in America, the burden of proof is on the plaintiff to show the statement is false. In the UK, the BOP is on the defendant to show the statement is true.

The arbitrator imposed the non-disparagement clause.

Sarah agreed to the arbitration process (she couldn't afford to do otherwise), but didn't specifically agree to the ND clause.

Cppcheck doesn't flag anything in Waffle Iron's example.

It also doesn't find anything wrong with:

std::vector<int> vec = {1, 2, 3, 4, 5};
auto it = vec.begin();
vec.push_back(6);
std::cout << *it << std::endl;

Which is another common example of how you can write memory errors without using C++ pointers.