A few years ago, my supervisor sent me a YouTube video of a CPU being explained as a cooking process. It appeared to have the end of result of a cooked meal! I cannot find the link at the moment (if I come across it later, I will link to it), but …
I am testing out variations of my App Histories package on High Performance Computing (HPC) systems. For now, these are timing exercises to find the most efficient deployment. I was thinking of how to explain some of this to a non-technical colleague and the image of Twister came into my mind. A limitation might be staying on one dot and moving within it, or the slight chaotic movement of processes shifting across cores. Needs some thinking and lots of refining, but maybe there is something there?
