Ok, I am a bit late (at least on my own planning) as I thought to post a TMW video last Friday, and one was nearly ready. But a very interesting discussion started at the end of the week makes me want to show something else (see https://futureofcoding.slack.com/archives/C5T9GPWFL/p1594276999116700 and thanks @Ivan Reese for starting it 🙂 ). In this video I use Scratch to show a quick and dirty example of a user that "extends" Scratch by creating some new visual "programming material" (term coined by @shalabh in the above discussion, thanks Shalabh 🙂 ) that is more expressive for the programming task at hand. The time was missing (two minutes is really very short!) to actually show the Scratch code that defines the behavior of the new visual programming material, but I am not sure it is the point here (but of course I can provide some screenshots/video of it if asked). This is a key idea for what I want to work on in the future. Giving (some) users the ability to create new visual programming material/artifacts/representations is an important part of my vision for the future of programming. https://archive.org/details/ogadaki_foc_tmw_2

this is great—one thing I really love about it is that the new programming material seems to function as a kind of embedded abstraction

Yes, that is cute. Nearly ties the code-canvas knot. I like how the wand is basically an instruction pointer.

Yes, I enjoyed using a flying cursor to represent the time that is going on. And in fact all this is only a visual counterpart of languages like IRCIS (https://github.com/batman-nair/IRCIS) from @Arjun Nair!

Making the instruction pointer first-class, tangible, "playable"/embodied.. I think this is very good. Participatory execution.