On pages 136 and 137 in The Clean Coder, Robert C. Martin describes how chips could be independently deployed thanks to a vtable:The solution was pretty simple. Each chip had to be decoupled from all  the others. Each had to be turned into an independent compilation unit  that could be burned independently of all the others.So I measured the sizes of all the functions in the application and  wrote a simple program that fit them, like a jigsaw puzzle, into each  of the chips, leaving 100 bytes of space or so for expansion. At the  beginning of each chip I put a table of pointers to all the functions  on that chip. At boot-up these pointers were moved into RAM. All the  code in the system was changed so that functions were called only  through these RAM vectors and never directly.Yes, you got it. The chips were objects, with vtables. All functions  were polymorphically deployed. And, yes, this is how I learned some of  the principles of OOD, long before I knew what an object was.I know the three kinds of polymorphism, but what is polymorphic deployment?
What's polymorphic deployment
object oriented;polymorphism
This is just Robert Martin being a bit flowery in his writing. Prior to Martin's work, a simple change in the program meant replacing all 32 EEPROM chips. By using pointers to functions, each of the 32 chips became independent of one another. That's all it means.