This feels so full of subtle qualifiers and weasel words that it generates far more distrust than trust.
It only refers to models used "broadly across all" customers - so if it's (a) not used "broadly" or (b) only used for some subset of customers, the whole statement doesn't apply. Which actually sounds really bad because the logical implication is that data CAN leak outside those circumstances.
They need to reword this. Whoever wrote it is a liability.
Sounds like it’s been written specifically to avoid liability.
> One of the biggest constraints on the retrieval implementation is latency
If I’m getting a multi line block of code written automagically for me based on comments and the like, I’d personally value quality over latency and be more than happy to wait on a spinner. And I’d also be happy to map separate shortcuts for when I’m prepared to do so (avoiding the need to detect my intent).
let's say if apple uses s3, they need to create bucket name "apple.com", and then we can find what aws account which apple is using.
This is outdated information, and not required anymore when using CloudFront.
And even in the past, you could use the S3 API to implement a reverse proxy without matching bucket and domain names.
If the language is garbage collected, or if the test is randomized you obviously don't want to look at the minimum.
Depends what you’re estimating. The minimum is usually not representative of “real world” performance, which is why we use measures of central tendency over many runs for performance benchmarks.
I think it's better to discard the two slowest, or simply accept the fastest as the correct. There's (in my opinion) no good reason to discard the best runs.
If the integer value is 1 (not zero), control flow transfers to label_1, if the value is 2, it transfers to the second label, etc.
Interesting! It's like a simplified switch statement.