Sometimes they're unavoidable, when you simply have no idea, or can't think of all the things that could go wrong, it's better to give an error code than a gene

Sometimes they're unavoidable, when you simply have no idea, or can't think of all the things that could go wrong, it's better to give an error code than a generic, something went wrong, message. I've had worse though, when a UX design specified a specific error message and a developer blindly followed it and simply remapped errors to the given message, ignoring what the actual error was, misleading the users and the developers. I've told UX to never include error messages again..