Success messages go unreviewed, and that is where many misleading UI strings hide

A commenter described a week spent trusting an SES 200 OK response, which only meant the email was accepted, not delivered, and the failure stayed invisible. The author argues error messages get scrutiny because annoyed users read them immediately, while success messages are written once and almost never reviewed. Such success text often overstates the outcome, reporting the server's step rather than the user's actual situation. The author suggests messages should state the user's state and next step, and that the best safeguard is to write the copy alongside the fix and pin it in tests, since style guidelines and linters cannot reliably catch misleading wording.