Earlier quoted context omitted.
Those of us who are good at addressing user-reported issues learn to do the same. No one in our industry seems much to teach this skill. I wonder why.
> No one in our industry seems much to teach this skill. I wonder why. It's pretty simple. In a company of any size, customer support is a separate job from development. Asking a programmer to field support calls is like asking an architect to trim grass.
Why Won't You Answer My Question?
111–112 of 112 posts
Re: Why Won't You Answer My Question?
#112Haha, 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…
Hah. You think most techies want to get informative error reporting from their users? This is the email I sent to my hosting company a couple of years ago when WHM (a component of cPanel) started doing something silly that broke my SSHD: sshd and ip whitelisting - there's a bug it seems If I go to whitelist my current ip in whm, it asks me to restart sshd to make the changes stick. If I do that, sshd fails to restart…
The response? 'Could you please send a video showing when the problem happens'.
bangs head on desk