3 ms·

Oh come on, it had a valid error message, it just had a cute header. Things like this are a reminder that applications are still made by human beings who can ma

Oh come on, it had a valid error message, it just had a cute header. Things like this are a reminder that applications are still made by human beings who can make mistakes. Sure, it may have been better If it said "Something went wrong:-(" with a note to take a screenshot and ask for help. But if you can be cute and get the same point across, it's usually better to be cute.

manigandham 4y ago
> "But if you can be cute and get the same point across, it's usually better to be cute." Why exactly? The entire point of the article and the many comments here are about how subjective, useless and usually aggravating it is.
- dec0dedab0de 4y ago
  I think the article and the comments are wrong. I prefer things to be a little bit fun, and I suspect most people in the real world do too. It's definitely better than some PR driven corporate speak. Now if you want to say that the errors should be more detailed, then sure. But don't punish me with a drab error message when I'm already annoyed about the thing not working.
  - manigandham 4y ago
    And again, it's all subjective. I suspect most people in the "real world" (whatever that means) do not actually find it fun, hence the vast majority of professional writing in other industries not having any emojis. Lack of emojis doesn't mean PR driven corporate speak either, and in fact both are on same level of equivocal communication.
layer8 4y ago
I disagree. Cuteness is not professional, and it makes you wonder whether the software was created with the appropriate diligence, and whether the user's needs are actually being taken seriously. If, say, the cook in a restaurant messes up your dinner, or the mechanic happens to accidentally scratch your car, you don't want them to get cute about it, especially when you're already annoyed. Yes, mistakes happen, but then please be professional about it.
- dec0dedab0de 4y ago
  If, say, the cook in a restaurant messes up your dinner, or the mechanic happens to accidentally scratch your car, you don't want them to get cute about it, especially when you're already annoyed. Yes, mistakes happen, but then please be professional about it. So you would rather them inform you of their mistake deadpanned without any show of emotion? You don't like when the waitress circles the refund on your check, and writes sorry for the trouble hope you give us another chance with a smiley face? Or when the mechanic says he'll have his body guy fix the scratch before making a crass joke and offering you a donut? Real life interactions are full of emotional cues, and personality. This is because it can often soften the blow of bad news. If you show me a picture of a puppy along with the error message I'm going to be a little less annoyed. That said, definitely show as detailed of an error message as you can along with that puppy.
  - esrch 4y ago
    I don't think that the examples that you have with the waitress and the mechanic are good comparisons, because they are "cute" after solving your problem. More accurate examples would be the waitress or mechanic saying "Oops, sowwy! Something went wrong." and leaving, without solving your problem. I'm also on the side of being professional while the problem still stands, because the user is most probably annoyed at the situation, and wants you to take it seriously. You can be cute after the issue has been resolved.

manigandham 4y ago

> "But if you can be cute and get the same point across, it's usually better to be cute." Why exactly? The entire point of the article and the many comments here are about how subjective, useless and usually aggravating it is.

dec0dedab0de 4y ago
I think the article and the comments are wrong. I prefer things to be a little bit fun, and I suspect most people in the real world do too. It's definitely better than some PR driven corporate speak. Now if you want to say that the errors should be more detailed, then sure. But don't punish me with a drab error message when I'm already annoyed about the thing not working.
- manigandham 4y ago
  And again, it's all subjective. I suspect most people in the "real world" (whatever that means) do not actually find it fun, hence the vast majority of professional writing in other industries not having any emojis. Lack of emojis doesn't mean PR driven corporate speak either, and in fact both are on same level of equivocal communication.

layer8 4y ago

I disagree. Cuteness is not professional, and it makes you wonder whether the software was created with the appropriate diligence, and whether the user's needs are actually being taken seriously. If, say, the cook in a restaurant messes up your dinner, or the mechanic happens to accidentally scratch your car, you don't want them to get cute about it, especially when you're already annoyed. Yes, mistakes happen, but then please be professional about it.

dec0dedab0de 4y ago
If, say, the cook in a restaurant messes up your dinner, or the mechanic happens to accidentally scratch your car, you don't want them to get cute about it, especially when you're already annoyed. Yes, mistakes happen, but then please be professional about it. So you would rather them inform you of their mistake deadpanned without any show of emotion? You don't like when the waitress circles the refund on your check, and writes sorry for the trouble hope you give us another chance with a smiley face? Or when the mechanic says he'll have his body guy fix the scratch before making a crass joke and offering you a donut? Real life interactions are full of emotional cues, and personality. This is because it can often soften the blow of bad news. If you show me a picture of a puppy along with the error message I'm going to be a little less annoyed. That said, definitely show as detailed of an error message as you can along with that puppy.
- esrch 4y ago
  I don't think that the examples that you have with the waitress and the mechanic are good comparisons, because they are "cute" after solving your problem. More accurate examples would be the waitress or mechanic saying "Oops, sowwy! Something went wrong." and leaving, without solving your problem. I'm also on the side of being professional while the problem still stands, because the user is most probably annoyed at the situation, and wants you to take it seriously. You can be cute after the issue has been resolved.