💡TL;DR
A “Something went wrong” message helps nobody. Log the real error and show users what they can do next.
Generic error messages make debugging harder and users more frustrated.
Instead of only showing:
Something went wrong.
Use a better pattern:
User message:
We could not save your changes. Please check your connection and try again.
Developer log:
SaveProfileError: API returned 500 for /api/profile
This way, users get a helpful message and developers still get the real reason.
Error-handlingDebuggingUXFrontendBackend
💡
Get a new Daily Dev Tip in your inbox
Subscribe to Stack Dev Life — free, no spam, unsubscribe anytime.
Subscribe free →