4 ms·

Or even worse, localized error messages. Good luck trying to 1:1 translate it back to English while remotely troubleshooting issues on your parents' computer.

littlestymaar 3y ago
Just write clear and explicit error message (like “Not a valid Microsoft controller”), you shouldn't need to Google it in the first place! You should still add an error code, so that people can look for additional documentation about the error on your official doc, but having obscure errors and assuming people will look on Google to see if someone on reddit or stackoverflow has more idea about what the problem could be is criminal laziness.
- numpad0 3y ago
  Your choice is a) "0x82d60002: Using unauthorised accessories compromises your ..." or b) "Error: Using unauthorised accessories ..." There is no c) "Not a valid Microsoft controller" option. Which one between a) or b) is more likely to lead to resolution? Note, Microsoft also offers phone and/or chat support to Xbox users.
  - littlestymaar 3y ago
    Where do your two options come from, and what makes you think there couldn't be an alternative? Also, what do your alternatives have to do with the question whether it's better or not for the error message to be localized? And why are error codes supposed to be 32bits long in the first place?
    - numpad0 3y ago
      TFA.
      - littlestymaar 3y ago
        This is the typical lazy answer, but there's a problem here: We haven't been talking about the article itself since half of the thread though, so I don't know what you're referring to. To get back to the topic, there are no reason why there couldn't be a good error message (there's no “two options” when you write your error messages) and if the error message is good enough so you don't have to Google it, you can and should localize it so the majority of the people of this planet could in fact read it. And you also want to put a error code available in case you still wanted to investigate about it, but there's little reason for this error code to be 32bits long unless you have 4 billion different possible errors in your app…

littlestymaar 3y ago

Just write clear and explicit error message (like “Not a valid Microsoft controller”), you shouldn't need to Google it in the first place! You should still add an error code, so that people can look for additional documentation about the error on your official doc, but having obscure errors and assuming people will look on Google to see if someone on reddit or stackoverflow has more idea about what the problem could be is criminal laziness.

numpad0 3y ago
Your choice is a) "0x82d60002: Using unauthorised accessories compromises your ..." or b) "Error: Using unauthorised accessories ..." There is no c) "Not a valid Microsoft controller" option. Which one between a) or b) is more likely to lead to resolution? Note, Microsoft also offers phone and/or chat support to Xbox users.
- littlestymaar 3y ago
  Where do your two options come from, and what makes you think there couldn't be an alternative? Also, what do your alternatives have to do with the question whether it's better or not for the error message to be localized? And why are error codes supposed to be 32bits long in the first place?
  - numpad0 3y ago
    TFA.
    - littlestymaar 3y ago
      This is the typical lazy answer, but there's a problem here: We haven't been talking about the article itself since half of the thread though, so I don't know what you're referring to. To get back to the topic, there are no reason why there couldn't be a good error message (there's no “two options” when you write your error messages) and if the error message is good enough so you don't have to Google it, you can and should localize it so the majority of the people of this planet could in fact read it. And you also want to put a error code available in case you still wanted to investigate about it, but there's little reason for this error code to be 32bits long unless you have 4 billion different possible errors in your app…