The article focused on the surface level of code, which I think is important. But the next level is where you can apply the same principles to the class hierarchy or how data flows.

I'm not sure if it's the right word but I've taken to using the word "locality", since it has prior usage in a similar concept in https://en.wikipedia.org/wiki/Locality_of_reference