Willing to bet that the backend that they are using doesn’t actually give any useful error messages.
Would they surface that to the user anyway? That’s something to log, not to tell the client that xyz service failed because of error 123.
I hate this attitude. Yeah don’t give the user stacktraces on error but if you give it a meaningful headline and go in detail, experienced users will be able to deal with the problem if possible. If you go Microsoft-error of mystic ways you will have people Google “unexpected error e34566xce” and they will see that it has 10 possible reasons so you don’t know what even went wrong.
Why use many words when few do trick but for system logs.
Looks up error EC10005…
“Network failed to do network thing”
Ok…
Tbf if the client fails to reach the server, there isn’t much more detail they can provide. At least it brings a little levity
Sounds like a “temporary” error message.
All my error messages are haikus.
We couldn’t log in.
Net didn’t do network thing.
Please try again soon.
Keys not aligning,
Username, password astray,
Entry gate stays closed.
