I trained the raccoons that visit my house at night. I started them out getting a peanuts from a water bottle. Then I tied the bottle to a rope. Then kept raising the bottle higher. At that point, I built an automated feeder system using a linear actuator activated by pulling the rope with the bottle attached. It had LEDs that were green / red to show when the feeder would / wouldn't dispense peanuts. It was all driven by an ESP32, it even had a web page on our LAN reporting how many correct / incorrect pulls were done. Over the coarse of a few nights they figured it out. Raccoons are so cool.
I always recommend his talk "A macro writer's bill of rights" [0] to people. It ties into some of the papers he has written, and also shows how nice it is to have a source->source optimizer. You write some code, and can the look at it after most of the common transformations (inlining, DCE, loop unrolling, constant propagation).
I spent some time reading the r6ra discussions and was blown away by the thought that went into the whole thing. There are very few parts of the semantics of R6RS that are actually bothersome. The only thing I really don't like is promises and the dynamic environment.
There are lots of cool papers Dybvig has published related to Chez Scheme that are relevant for anyone hacking on compilers. Specifically, destination-driven code generation is really neat.
If powerhouses like ARM, Apple, Google, Microsoft and even Linux kernel admit not being able to, now even pushing for hardware memory tagging as the only remaining way to fix C and its influence on C++/Objective-C, you are indeed a top expert.
