• SavvyWolf@pawb.socialEnglish
    3·
    11 months ago

    Willing to bet that the backend that they are using doesn’t actually give any useful error messages.

    • GarytheSnail@programming.dev
      2·
      11 months ago

      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.

      • Johanno@feddit.de
        3·
        11 months ago

        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.

        • azertyfun@sh.itjust.works
          1·
          11 months ago

          Anyone who says error codes shouldn’t bubble up to the user are incompetent. Either because an incompetent PM infantilizes their users, or more likely because incompetent teams don’t/won’t take an extra 10 minutes to do proper error handling (and they suffer from this as well since they’re the ones who spend hours deciphering the result of a try {} catch(_) { error("we did a fucky wucky uwu") }).

  • PeriodicallyPedantic@lemmy.ca
    1·
    11 months ago

    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

  • stewie410@programming.dev
    1·
    11 months ago

    Had the displeasure of using the modern EA app the other week – completely refuses to launch my copy of Jedi: Fallen Order in the foreground after a single play-session (Steam -> EA just doesn’t work for some people).