I looking for an article that I read once but cannot find now.
The author described his approach for error messages: instead of displaying (and logging) a code (e.g. 987345345EXRTET), he would always display (and log) a series of words (e.g. dolphin pancake Wednesday), and that series would uniquely identify the error in the logs.
Users inevitably found these error messages novel, refreshing, intriguing, memorable, and useful--useful because if they ever needed to talk to Support about something, the tech support could immediately find the occurrence of that error by searching that particular string.
Did anyone else see that article (or could you flesh out this approach better so that I could actually implement it)?