It's not the only drug that suppresses appetite, but GLP-1 agonists (Ozempic, Zepbound, etc) appear to work for a larger percentage of the population, and significantly outperform previous appetite suppressants.
There's also findings that suggest that it goes beyond simply suppressing appetite, but also manipulates the "reward" center in the brain. Individuals who take it to lose weight find that they have reduced desire to drink or smoke, suggesting it's less that they struggle with appetite and more the medicine helps overcome addictive behavior.
Tom7 implemented some of this with his Learnfun and Playfun (https://www.youtube.com/watch?v=xOCurBYI_gY) -
It looks for lexicographical changes to bytes in memory (i.e., one byte seems to almost always increase, and then when it suddenly decrements, a neighboring byte is incremented) as a way of calculating memory location for increasing values (score, x-position), and similarly detects bytes that generally seem to decrease (lives).
It then tries to play the game, choosing inputs that increase the values that should be increasing (move right, gain lives), or tries not to decrease the values that are decreasing (don't die).
It looks like Autocanonizer depends on (the now defunct) Echo Nest (http://the.echonest.com). Spotify bought it back in '16, and the site stopped serving content sometime mid-May of 2020.
> People get so enamored with trying to make REST APIs into this rigorous thing.
It is a rigorous thing, though. It's a standard, and one that has existed for a very long time.
> I would prefer HTTP status codes just go away altogether. Those are for the web browser software to do things like navigation, not for APIs. Same with HTTP verbs.
Verbs and status codes are fundamental for APIs that consume REST endpoints.
I totally understand thinking that vanilla REST is not the perfect model for every case. Maybe you should be using SOAP, or GraphQL, or HATEOAS. What a seasoned engineer shouldn't be doing is abandoning a shared specification and expecting everyone else to comply.
If I am using a third party's API and they serve nonsensical status codes (4xx when their DB is down, 2xx to let me know something failed), I will reach out and ask for them to fix their bug. If they tell me that the error code is deliberate, I will probably look for a more sensible vendor to work with instead.
I visited the UK recently, and I was quite impressed by the accessibility of their banknotes compared to the US ones:
* braille on the notes
* different colors for different denominations
* different sizing for different denominations
The UK notes are far more accessible to the blind and the illiterate, and it becomes basically impossible to accidentally include a £100 note in a stack of £5s.
They also have holographic printing like the US notes, but theirs are full images embedded in transparent windows.
I know that it would be basically impossible for us to do likewise (our currency is designed to be backwards compatible, and the vending industry would probably throw a fit if you changed the size of the bill on them), but one can wish.
There's also findings that suggest that it goes beyond simply suppressing appetite, but also manipulates the "reward" center in the brain. Individuals who take it to lose weight find that they have reduced desire to drink or smoke, suggesting it's less that they struggle with appetite and more the medicine helps overcome addictive behavior.