Obviously the throwing of the correct exception is something the outer program will observe - but to what extent do they care about the error message?
Parseexception error validating the model Sexdatingsite
But if you're running some checks on outside input, this is because you expect some messages to fail - and if a failure is expected behavior, then you shouldn't be using exceptions.
The second problem with code like this is that it fails with the first error it detects, but usually it's better to report all errors with the incoming data, not just the first.
When we're doing a refactoring, the rule is to avoid changes in observable behavior.
In situations like this, such a rule leads immediately to the question of what behavior is observable.
But I've now set things up ready to start replacing exception throws with manipulating the notification.