>The name implies responsibility, so poorly named things imply things they don’t actually do.
Joshua found that finding a name that clearly articulates the essence of the responsibility allows oneself and others to adapt the system with much more facility.
Knowing the essence of a responsibility is not enough. That knowing needs to be clear to others, so that when they look at the code, they understand the true nature of that responsibility. If not, assumptions will be made that frustrate the ability to modify it.