what do you think of "code that changes together, stays together" for explaining the SRP?

i've found minimising shotgun changes to bey favourite and most productive guiding light when refactoring.