Wait til the OP learns about the Easy Bake Oven.

I call BS.

I’m Canadian and my parents immigrated here from England before I was born. I have a UK passport as well as a Canadian passport.

I’m not English-Canadian, I’m just Canadian. No one hyphenates in Canada, and you cannot say that Canada has any more unifying cultural heritage than the USA.

That number is supposed to be how much of the tariff that the exporter passes through to the importer. Essentially this is a measure of how much the producers lower their profits to lower the price to compensate for the tariffs. In other words how much the producer “pays for” the tariffs.

This factor is “backwards”, in that it doesn’t represent how much the producer swallows, but how much they pass on to the importer. Trump’s calculations assume that the producer only passes on 25% of the tariff price increase, but the experts say the number should be much closer to 95%.

I have to idea what “4” means.

I’m not no sure. 90%+ of these services are commodities and nobody gives a damn who the provider is from a technical perspective. There’s no physical component, so it’s literally a matter of signing a contract, spinning up a server/service, move the data and point everything to the new service.

And yeah, there are technical issues that come up, and nothing is ever that easy. But think about how fast many, many companies were able to sort that kind stuff out when the had to when COVID hit.

And that’s the thing. Cloud service disruption can be an existential crisis, so why would you leave it in the hands of a hostile foreign power?

The US has been there before with the Nullification Crisis of 1832. https://en.wikipedia.org/wiki/Nullification_crisis?wprov=sfla1

He’ll, if the requirements were gender neutral, then every astronaut would be a woman based on weight alone.

Buy Canadian is best, but anything will do if it isn’t American.

Groove Salad plays constantly on all the Nest devices through my from morning to night.

In the very first real programmer job that had, back in 1986, the IT department estimated that they had a 51 man-year backlog of development work. That would have translated to two or three calendar years of work. Probably more, considering how crappy estimates always are, and the always under-estimate.

It turns out that this is pretty much the industry standard. Virtually ever place I worked for the next 35 years had a similar size of backlog. And that backlog isn’t standing still, either. All you can hope is that 3 more years worth of new requests don’t come in during the two years it takes to complete what you already have.

Some of those new things are going to have a higher priority than stuff that’s already in the backlog. The reality is that some item that’s down at the low end of the list is going to get bumped down, again and again, and never get done. Or it’s going to someday become an urgent priority that can’t wait any more.

So the pressure is always intense for the developers to go faster, faster, faster. And the business doesn’t understand or care about good engineering practices, even though the shit hits the fan when a critical bug gets released to production. And God help you if that backlog of 51 man-years has grown to 70 after a year because of the technical debt you introduced trying to go faster.

The fight to rein in scope is constant. At that first job, the head of the department told us, “to build Volkswagens, not Cadillacs”. It was laughable, because they were struggling to keep up while building Skodas.

You can’t just add more programmers because the productive backbone of the development team is a group of programmers that have all been there for at least 5 years and they are domain experts. It’s going take at least 5 years to bring new hires up to that level of knowledge.

And that’s all three sides of the project triangle: scope/quality, resources and time. You can’t meaningfully add resources, scope’s already stripped down to bare bones and the time is too long.

And the truth is that every one of those projects in that 51 man-years backlog is important, even critical, to some aspect of the business. But the development process is unfathomable to muggles, so can’t you just go faster? Can’t you wring a bit more productivity out of those domain experts?