• Johanno@feddit.de
    link
    fedilink
    arrow-up
    19
    ·
    edit-2
    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
      link
      fedilink
      arrow-up
      9
      ·
      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") }).

    • GarytheSnail@programming.dev
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      11 months ago

      There’s nothing a user is going to be able to do if this is a problem with the backend. The person I replied to did specify backend, right?

      • Johanno@feddit.de
        link
        fedilink
        arrow-up
        5
        ·
        11 months ago

        If your code gives attack surface by information about what went wrong maybe you should not even deploy anything. If your code needs to be secret to be secure your code is anything but secure.

        • MonkderZweite@feddit.ch
          link
          fedilink
          arrow-up
          4
          ·
          11 months ago

          Not code but internet. A often seen error is letting Appache/Nginx display their name & version in 403/404 pages. First step in planning an attack.