Comment on Oops, something went wrong!

• hperrin@lemmy.ca ⁨11⁩ ⁨hours⁩ ago

  I can’t speak for the other user’s claim, but I’ve worked at Facebook, Google, and LinkedIn, and have written plenty of error messages. When I write a message like these, it’s specifically because the user can’t do anything about it. I’ll log the error to our internal error tracking systems with actual information about it, then give the user a generic message.

  If it’s something the user did wrong, and they can fix it, I’ll absolutely give them a message saying that. Usually I won’t even let a user submit a bad request, but sometimes users will bypass frontend restrictions to submit it, so the server always needs to validate it again anyway. The fact that plenty of users won’t even read the message I write is kind of annoying, but at least the users who do read it will know how to fix it.

  I’ve tried sending detailed error messages before, and that invariably results in users submitting support tickets and forum posts for things that aren’t helpful. You learn pretty quickly what kind of messages are helpful and what kind aren’t.

  source

  • unhrpetby@sh.itjust.works ⁨10⁩ ⁨hours⁩ ago

    I would appreciate the detailed error responses even if the developers don’t think it would be of use to them.

    When a project has unexpected downtime, and they do a postmortem explaining exactly what part of their infrastructure failed, what steps they took to resolve it, and how they will prevent it in the future, that is great.

    I appreciate transparency. Of course, to expect this from a large corporations is expecting a pig to fly, but detailed error messages are one more step away from “We are the cloud” and one step towards “We are real people providing a service which operates on server infrastructure consisting of…” Its transparent, down-to-earth, and respects people who do want to see behind the scenes.

    One company I used even had a white paper explaining their infrastructure as a whole.

    This is all much appreciated.

    source

    • hperrin@lemmy.ca ⁨9⁩ ⁨hours⁩ ago

      I want you to really pay attention to the last paragraph of my previous comment. It’s the most important part. You might like having more information that doesn’t help you, but that comes at the cost of thousands of useless tasks and posts that all have to be manually closed. It’s not only not helpful to give the user detailed error messages in a lot of cases, it’s actively harmful to a business. It doesn’t make any business sense to tell a user that a cache layer host or a db shard is down. As a developer of these kinds of systems, I’m not going to give extra information that you don’t need just to make a few users happy that they get a peek under the hood if it means hurting our support staff.

      source

      • unhrpetby@sh.itjust.works ⁨9⁩ ⁨hours⁩ ago

        How is a user sending a support request containing the information: “Site not working. Error message: A surge in requests is overloading the server. Everyone is being ratelimited” Any different from them just saying “Site not working.”?

        If they were going to submit an issue for a problem that is already known, why would the error message significantly change the difficulty of dealing them?

        source

        • -> View More Comments