I learned about Turing Machines as a CS student a long time ago, and got the false impression that he was only involved in theoretical pursuits (theory of computation, algorithms for cryptography, etc.). It was only after reading this book that I learned how much he had contributed to the design of actual computing hardware.
> trying to avoid running codes that revisited adjacent memory locations too frequently
And today, it's exactly the opposite: we try to write code that has as much locality of reference as possible so that we can avoid expensive cache misses.
The biography Alan Turing: The Enigma (which I highly recommend) also goes into a lot of detail about the early computers that Turing worked on:
https://www.amazon.com/dp/069116472X
I learned about Turing Machines as a CS student a long time ago, and got the false impression that he was only involved in theoretical pursuits (theory of computation, algorithms for cryptography, etc.). It was only after reading this book that I learned how much he had contributed to the design of actual computing hardware.
> trying to avoid running codes that revisited adjacent memory locations too frequently
And today, it's exactly the opposite: we try to write code that has as much locality of reference as possible so that we can avoid expensive cache misses.