Just started working as system developer and dislikes the labeling of a home made exception: HumanErrorException. In my view, there is no such thing as a human error in a computer based system - just users who don't do as developer expected. So the real label for the exception would be DeveloperNotTakingUserBehaviourSeriouslyException, but I think there will be a fight when I relabel :)Have you ever seen a wrong labeled exception (type, class or method) around? If you did, what did you do with it? 
Naming of types, classes and exceptions sometimes go wrong
exceptions
When I find something wrongly named in my opinion, I usually inform the person who made it and tell him the name I am suggesting. If I have the authority and seniority I will just inform and refactor. If I do not have the authority I will explain to him but if he is not convinced I will leave it as it is.Regarding your case, I agree there is nothing called HumanErrorException and there is nothing called DeveloperNotTakingUserBehaviourSeriouslyException either. If the exception class is written in code, it means that the developer is aware and taking care of it already. Also Exceptions should be named after the error happened itself like ValueOutOfRangeExpecption, NullValueException and so on.