By that metric we should just pack it all up and call it a day on computing in general; because even despite literal trillions of dollars being spent on it, we still haven't found a way to make it secure.
No; the person I replied to line about "having to transition these by the end of the year" was a reference to a fact that Apple's publicly announced deal with Qualcomm expires this year/early next year.
And perhaps more importantly for the final price, if you’re paran^W concerned enough about security to the degree of commissioning custom iPhones without cameras, you’re also not going to let a random guy from the street drill into them.
(You also need to remove the front facing camera, which is also a more involved operation.)
AIUI the process of building asset packs and compressing them can mean that modifying a single texture can mean complete reshuffling of the resulting file; and that means redownloading the whole compiled "pack".
You can buy games directly on Steam without buying a physical box too; I presumed from context it was clear I was referring to retail, physical editions.
It's mandatory for literally all (native) PS5/XSX games; because that means the games can rely on SSD speeds and not worry about supporting fetching data from the spinning disks.
>If I am in the middle lane (lane 2), and I realize I need to get into the leftmost lane (lane 1) to make a turn, but lane 1 is too full for me to simply move into it without affecting others, then I would have no choice but to cut someone off.
...you could just miss your turn, instead of cutting someone off?
I've seen you comment along those lines before, and I think you're both right, and terribly wrong.
By all measures, the way you describe any hiring processes you've designed and had input on designing the metric and the work sample, probably is both high in signal, and not very arbitrary in scoring. They sound genuinely and refreshingly good. Maybe one day I'll interact with one :)
But man, that is very much not how work sample tests work in _a lot_ of places out there.
Places with actual, formalized rubrics for what constitutes a "pass" or a "good" score are very rare, it's almost always just based on vibes of whatever person is reading your code. If there _are_ formalized rubrics, then they have "suggested allowed time" that is incongruous with what the requirements for a "pass" actually are.
All of that is downstream, fundamentally, from the design of the tests not being taken very seriously by the people doing that. And because they're not actually thinking about it very deeply (or they're not allowed to because of time constraints or whatever); "sit down and redesign this task from first principles thinking about what AI enables now" is just not something that happens, and you just get people increasing the scopes of the project blindly.