4 ms·
> This includes vague "something went wrong" errors. Azure devops at one point used to give the user a stack trace pop up… just MS UX things. I imagine most us
by PUSH_AX 3y ago
> This includes vague "something went wrong" errors.
Azure devops at one point used to give the user a stack trace pop up… just MS UX things. I imagine most users see that and think what the f am I supposed to do with this information?
I guess my point is sometimes whoops is probably a better message when the issue is technical.
- charles_f 3y ago> sometimes whoops is probably a better message when the issue is technical. Except that you can't do anything with it either, and particularly not report it. Same goes for "ask help from your system admin".
- PUSH_AX 3y agoBut this is my point. It’s like that old joke, 400: you fucked up, 500: we fucked up. What exactly can you do when the issue is on the service side anyway. My expectation is most good software has something like sentry anyway, reporting should be a thing of the past
- throwaway50662 3y agoSometimes if you know what failed or at least get a hint of where the error is, you can try going another way, adjust some meta/data, wait for a bit, don't use a particular feature...