6 ms·
I completely disagree with the tweet. Apps usually show this kind of message when the user can’t do anything to fix the problem. If the “code monkeys” are work
by mypastself 4y ago
I completely disagree with the tweet. Apps usually show this kind of message when the user can’t do anything to fix the problem.
If the “code monkeys” are working on it, what’s the user going to do about a crashed database or any other server-side error? If you can do something to fix the issue, the app will usually give you that information.
Of course, the app might be clearer and tell the user to retry or contact the administrator. But a generic error message usually implies server-side failure anyway.
Perhaps this person expects to receive server credentials as well?
- mrguyorama 4y agoThe vast majority of the time I've run into programs and apps giving me a vague error message, you can look behind the scenes at logs and Event Manager and similar. It's almost always a dumb software dev made a dumb assumption about a specific file being in a specific place and just chose to not check the return value for errors and it dies. If you log the API calls and debug it yourself, you will be able to find the stupidity and delete/fix/move whatever errant file is causing the issue. So often, literally returning the raw API return value in the "Something went wrong" window would be the best information to provide. It's laziness, it's devs thinking "Users are stupid". It's NOT hard to put a checkbox in the settings somewhere that says "show advanced error details" if you are so damn terrified of average people seeing "Scary" error messages.