31–40 of 112 posts
this is just an example of low-IQ people trying to do high-IQ things, and failing publicly. i don't think it's really much more complicated than that.
Earlier quoted context omitted.
Change the first line of your error message to, "Important: Please mention the following error number when contacting support." you told us that is what you need - but did you tell the user?
Doesn't matter what the error message is. It's very unlikely they're reading the error message at all. And yes, I've tried what you mentioned. I did fib a bit though. There is one error we get emailed to us regularly. It's a 403: {"code": "Forbidden", "message": "You do not have access to this API feature because you need to be a member of role [ROLE]. To get access, follow this link to our role request page here: ht…
How about. "Forbidden. Please request access by following this link: http://internal/?requestguid=GUID&custn=CUSTNAME
Your request will be handled within 24 hours."
That link?
If they click the link - which they will - you have all the information they should email you (but don't.) Because you told us all you need is the GUID.
Remember: Error messages are literally an API between you and the human. If the human isn't doing what you want, you need to debug your API code until the human is doing what you want. The human is like a device! It might be flaky, but you're stuck with it. So debug your API code (the error message) until you work around the flaky humans.
Haha, yeah go ahead and try to fight this battle. You'll lose. I'm constantly baffled by bug reports I receive. From other people who work at my company. A tech company. A large one. You've heard of it. We log every operation in our API. I cache errors, and the API returns a JSON formatted error with a GUID that correlates to the operation that failed, so if I have a GUID I can look at exactly what happened every ste…
Oh god yes. I don't understand why it's so hard for people to report a bug. I don't think other fields suffer from this as much. No one goes to the doctor and says: - I don't feel good - What are your symptoms? - I don't know, I just feel bad. It's usually in the form of: "I have a sore throats and running a fever, it began x days ago", etc What is it about computers that makes people throw their hands in air and say…
Once it reaches the point where the problem has been clearly isolated and the soliton path identified, I usually don't count it as a problem anymore.
Haha, yeah go ahead and try to fight this battle. You'll lose. I'm constantly baffled by bug reports I receive. From other people who work at my company. A tech company. A large one. You've heard of it. We log every operation in our API. I cache errors, and the API returns a JSON formatted error with a GUID that correlates to the operation that failed, so if I have a GUID I can look at exactly what happened every ste…
If the questions come by email, delete the email. Not a difficult operation.
If you encounter stupid questions due to your participation in a website, stop visiting that website, or stop answering questions on the website. Not a difficult operation.
The people who write long screeds about answering/asking questions are all masochists.
this is just an example of low-IQ people trying to do high-IQ things, and failing publicly. i don't think it's really much more complicated than that.
It's not about IQ, it's about knowing how to learn. Being able to teach yourself something is a skill, which most people don't realise. Knowing how to find information isn't something you're born with.
1. what did you do?
2. what did you get?
3. what did you expect?
Haha, yeah go ahead and try to fight this battle. You'll lose. I'm constantly baffled by bug reports I receive. From other people who work at my company. A tech company. A large one. You've heard of it. We log every operation in our API. I cache errors, and the API returns a JSON formatted error with a GUID that correlates to the operation that failed, so if I have a GUID I can look at exactly what happened every ste…
Then, you had a large group of people who had some degree of imposter syndrome and felt inferior to the first group, partly because the first group seemed so confident. They would avoid situations where they might get called out or blamed. Often their insecurity would lead to more mistakes or poor explanations once they did occur.
I wonder if this same phenomenon might be occurring in your situation?
I imagine in corporate environments people want to seem favorable to their bosses for bonuses and what have you. Also, and especially at large tech companies, you would have procedure, process, and tooling, that was relied on heavily and whenever something out of the ordinary cropped up that the tooling did not hand hold them through, would put them in a loop.
Earlier quoted context omitted.
Doesn't matter what the error message is. It's very unlikely they're reading the error message at all. And yes, I've tried what you mentioned. I did fib a bit though. There is one error we get emailed to us regularly. It's a 403: {"code": "Forbidden", "message": "You do not have access to this API feature because you need to be a member of role [ROLE]. To get access, follow this link to our role request page here: ht…
So you need to lie in your error messages and come up with a message that will get emailed to you. How about. "Forbidden. Please request access by following this link: http://internal/?requestguid=GUID&custn=CUSTNAME Your request will be handled within 24 hours." That link? If they click the link - which they will - you have all the information they should email you (but don't.) Because you told us all you need is th…
"If you ignore that link and instead email this to us, we'll try to get back to you within 5 business days."