What is with the modern obsession with renaming things? Does your boss measure your performance by the number of lines needlessly changed in the code or something? Before refactoring support was the must have feature of IDEs, we had stable APIs to program to. Now some kid that grew up with his attention span crippled by the internet and smartphones wants to change the names of everything every five minutes.
If you want to keep a changing source code base as easily understandable as possible over time without confusing future programmers who have to work with it, you will need to refactor and rename as you go.
As requirements and thus code changes, the names of your functions, classes and files will become less correct, and lead future maintainers on a wild goose chase.
Keeping names appropriate by changing them is protection against future confusion and wasting of time.
It's actually a long-term solution to a long-standing problem and has little to do with crippled attention spans. It requires concentration to keep the names of things accurately matching their content. This investment of concentration will pay dividends on non-throwaway code.