This is awesome. Does anyone know if there is a library for the amazing optical codes that apple uses in its device transfer? I know they have a custom patent for it so I don't know if its something anyone has tried to recreated...
Agree, in fact this wonderful book calls this out, stating:
As DuckDB is an analytics database, it has only minimal support for transactions and parallel write access. You therefore couldn’t use it in applications and APIs that process and store input data arriving arbitrarily. Similarly when multiple concurrent processes read from a writeable database.
For my Masters degree, most of my courses were absolutely like this. Our assignments were difficult and heavy. There was no expectation that you should complete them without Google or reference material.
In contrast, the "final exams" were either non-existent or extremely easy and account for only 10-20% of the grade, where they existed.
I really liked this approach. Make your assignments very difficult. Alternatively, give difficult 10-15 minute quizzes every other week. IMO, it's a much better way of evaluating students.
I was talking about the grand-parent comment's method:
> You can check you’re right if (a) the first digit of the result is 1 less than the number you started with
The first digit of the result is 2 ... And the number that you started with is also 2, which is not 1 less... I guess I am not smarter then a 5th grader
Wow! You definitely are smarter than me, the gp, at least! You’re right that my claim isn’t right in general. Hell, not even past 10, I can now see!
I’m curious, how did you find that counterexample? I kind of ‘overfitted’ my mental model to the first 10 integers. But as a statistician I’m only in the business of being approximately right...! Nice catch.
23x9=207 starts with 20 which is 3 less than 23... 24x9=216, and 21 is 3 less than 24. 11x9=99 and 9 is 2 less than 11, 12x9=108 and 10 is 2 less than 12. So 0-9 are offset by 1, 10-19 are offset by 2, 20-29 offset by 3, 30-49 offset by 4?
This really is great to see, but it’s clear from their careful wording that the google takedown of the recent widevine l3 repository won’t be reversed:
> And our reinstatement, based on new information that showed the project was not circumventing a technical protection measure (TPM)
It's kinda pointless to reverse that takedown. You can find it elsewhere, and Google plans to revoke the key in Q1 2021 after increasing/changing the obfuscation on widevinecdm.dll.