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?
That’s probably how the penguins got included.
The US has been there before with the Nullification Crisis of 1832. https://en.wikipedia.org/wiki/Nullification_crisis?wprov=sfla1
This just in: Water is wet!!!
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.
It’s a close call, but I think the IOC just edges out FIFA in overall corruptness.
I got confused about which side not to believe when one of the most corrupt governments on the planet starts mucking with one of the most corrupt organizations on the planet.
I fixed it by installing Shazam. Since then I haven’t paid any attention to it.
Except I’m not actually talking about spelling, per se, but about attention to detail. Spelling errors in a resume is just sloppy rubbish.
As an IT/Development manager, I only had one role that I hired for where the skills for getting the job matched the skills for doing the job: Business Analyst. Not job entailed presenting information clearly, both written and verbally. So I expected the resume and cover letter to be organized and clear.
Programmers, on the other hand, I wouldn’t expect the same level of polish. But I would expect a complete absence of spelling errors and typos. Because in programming these things count – a lot.
A lot of the people that applied, and that I hired, did not have English as a first language. So I gave a lot of latitude with regard to word selection and grammar. But not spelling. Use a goofy word or two, but spell them right.
I figured that most people were highly motivated when writing a resume – about an motivated on you can get. And if not level of motivation cannot get you to take care, then you’ll just be a bug creation machine if I let you touch my codebase.
It goes really well with YAGNI. Also DRY without YAGNI is a recipe for premature over-architecting.
This is also one of the main benefits of TDD. There was a really good video that I can’t find again of a demonstration of how TDD leads you to different solutions than you thought you use when you started. Because you code exclusively for one single requirement at a time, adding or changing just enough code to meet each new requirement without breaking the earlier tests. The design then evolves.
I’ve always heard of your “post-architecture” referred to as “evolutionary design”.
Many, many years ago I used to have two Wyse50 terminals, running split screens each with two parts. I did a lot of support on remote systems (via modem!) and I would have a session on a customer system, source code and running on our test system and internal stuff. I didn’t have space for a third terminal.
At another job I had an office with a “U” shaped desk. I would spread printouts across half the “U” and swivel around between the computer and the printouts.
L’esprit de l’escalier