True or False:
When refactoring legacy methods (e.g. adding a parameter or deleting altogether), it is guaranteed not to break anything as long as I update every reference in the code base, based on a global find in org metadata for the method name that searches all classes and pages, given that the method's access modifier is public with no annotations, and is not a getter.
The no annotations bit seems to make searching more metadata types needless, since flows/processes require @InvocableMethod, JS static resources need @RemoteAction, aura bundles need @AuraEnabled, and integrations require REST annotations or WebService keyword.
I want to be defensive in my approach, but this legacy method already has 3 needless method overloads, and I feel like I'm sacrificing readability for (perhaps unjustified) precaution to add another overload. I want to be cautious but not overly cautious.