Because I'm.. not young.. all throughout my education we were 'awarded' 4 points for an A, 3 for B and so forth to calculate Grade Point Average (GPA.)
Due to this system I have always considered A > B > C, etc.
Some of my children lived under a different regime in elementary school, which common core and non-letter grading assessments. Target, Near Target and Below Target.
A = 1, B = 2 reminds me of cryptography for some reason. That's probably due to reading Neal Stephenson.
I think you might find that the larger metropolitan areas are as you say. As one gets away from the coasts and into more rural areas you'll find smaller museums. Museums that are very bespoke and/or focused on a narrower curation target, etc.
Marques Brownlee recently published a video about the Humane AI Pin (device) [1] and I noticed this book in some of the device shots, found it curious and had (incorrectly it seems) assumed it was some kind of internal Google swag.
My father owned a rural feed store until I was 6 or 7 years old (the early 80's.)
Other than incubators full of chicks and ducklings, and bottle feeding young livestock fresh from auction - swiping cow magnets off the shelf to play with was a favorite pass-time. :)
In those days I can't imagine anyone really cared what happened to the magnets after they went into the cow.
Perhaps something happens in the slaughter house to clear out whatever has gotten into the gut and stomachs - for the sake of meat grinding machinery?
Feature Request: I'd love to see the ratio of successful points to number of times the ball traverses the circle. I think others have already said things about scoring mechanisms for faster taps, I wonder if there could be one around a sweet spot on the line (earlier is better? Later?!)
Would love to hear your thoughts on pipenv as a real-world user of python environments. I leave it on the table that your current solution just works and you have never considered pipenv. ( I am not associated with pipenv. I've seemingly organically gravitated to it lately. )
I have to assume someone is using the software therefore there is some tribal knowledge of what it does? Otherwise this is maybe SAAS software that users use and some functionality is exposed that would allow you to begin decomposing backwards toward expected input/output. You're almost black-boxing at that point.
I will admit that I have, on very rare occasion, scream tested a piece of software running on a server that nobody would claim ownership or knowledge of either on the eng. team or within the org.
Have you used input/output proxy logging shims in these situations? They've been so invaluable to be in finding those weird edge cases that come up in 'orphaned software' projects as well as 'ancient legacy platform' migrations ;)
As someone who runs terminal obsessed engineering organizations I can see a wider implication for team docs. Would love a distributed version of this. I suppose we could do something with git, etc but the sync cycle would inevitably kill forward momentum of usage. Bonus points for a web server for those who aren't terminal obsessed.
Due to this system I have always considered A > B > C, etc.
Some of my children lived under a different regime in elementary school, which common core and non-letter grading assessments. Target, Near Target and Below Target.
A = 1, B = 2 reminds me of cryptography for some reason. That's probably due to reading Neal Stephenson.