3 ms·

> how messages like "Oops! Something went wrong. Please try again" actually results in a better experience for anyone at all Didn't you just explain how? > c)

> how messages like "Oops! Something went wrong. Please try again" actually results in a better experience for anyone at all Didn't you just explain how? > c) if it's a transient error that's not the user's fault, explain that and suggest at what point they should retry Many times when I've sent this type of error but it's not actually transient was a mistake in misclassifying the error. So if the code doesn't actually know it's a or b, it's not surprising it defaults to c.

wizofaus 4y ago
> Didn't you just explain how? "Something went wrong" I don't consider as a message that provides a good experience. Actually I didn't even mind the example given in the original article "Token not provided in guest headers", though that very much sounds like a b) error, where it's not transient but there's nothing the user can do about it, but at least they have some sort of unique identifying message/code that can help support figure out the problem. And sure, classifying errors can be tricky, and it absolutely requires following best-practices throughout the codebase to ensure that errors are passed around in a reasonably consistent manner where you can distinguish transient from non-transient errors, or errors where the user can take reparative actions. But the end result makes everything vastly better for the user and developers/testers etc., so is well worth the investment.