Like, from reading, this I have no idea what the article is about.This is a not-great summary...
Like, from reading, this I have no idea what the article is about.
Edit: A better summary.
Apple has a corporate structure based in Ireland consisting of two companies (ASI and AOE) setup in 1991 and 2007. This is to minimize tax burden.
The European Commission has concerns that this structure isn't legal. There have been a series of court cases (2016, 2018, 2020) about this. The current status is that Apple is fine, but there was a filing for appeal in 2021 and an opinion published in September 2023 that this should be reviewed.
(The CJEU published a press release about the recent opinion in November a few days ago, which is why this is news.)
This would cost Apple $13B. Apple's Q3 profit this year was $23B.
Entirely separate from the EU case, Apple will pay $25M to the US Department of Justice for violating the Immigration and Nationality Act.
To hire a nonresident alien in the US (and to sponsor them for a green card), employers must demonstrate that the position could not be filled by an American citizen or permanent resident. Typically, this is done by advertising the position where only Americans can apply.
Apple technically did the advertising, but they required applicants using this process to mail paper applications. The DOJ found that this did not give proper advantage to Americans.
The article is comparing to the dynamic programming algorithm, which requires reading and writing to an array or hash table (the article uses a hash table, which is slower).
The naive algorithm is way faster than the DP algorithm.
I think the issue is that customers can escalate directly to SRE.
SRE is supposed to work on the health and reliability of the service. It does sound like there is a reliability issue when loading large datasets. But this should be project work, not incident response work.
Is your service violating your internal SLOs when this happens?
Where I work, customers escalate to a support team, who tries to work with them. It's only after the support team decides it's a product issue that it makes it to SRE. Even then, 90% of the time, the support staff will file a ticket to be handled at business hours rather than page SRE.
If this auto scaling delay is expected, I'd try to do two things:
Produce better error messages, so that the customer can know what's happening and hopefully not need to escalate.
Work with the rest of the company (typically the Product or Support teams if you have them) to make sure customers understand these limitations.
Edit Oh, also don't let customers page you for known limitations. Design a better process around this.
And if it's that bad, SRE should invest in project work to make the autoscaling less painful.
Edit: Your service should return some kind of client error (i.e. exempt from SLO) in this situation. In gRPC, that would probably be RESOURCE_EXHAUSTED, and the error message should be something like "Yo your DB is out of disk, chill out while we fetch more disk. To avoid these errors in the future, pre-scale before large writes."
Dude is old. This next election will be the last of his career. He knows that. Doing what he thinks is "right" is way more important to him than the approval rating.
Aside from the atrocities that are happening, the discourse around this war is so emotionally draining.
It's not hard to find islamophobic hate speech in communities that support Israel, because there's plenty of people that conflate Hamas with normal Palestinians.
And it's not hard to find antisemitic hate speech in communities that support Palestine, because there's plenty of people that conflate the Israeli government with normal Jews.
M: "Mega": 1000^2Mi: "Mebi": 1024^2m: "Milli": 1000^-1