Meme transcription:
Panel 1 of 3: A cute dog looks asks, “pls fix problem??”
Panel 2 of 3: The dog has become upset and says, “No Info!!”
Panel 3 of 3: The dog looks very angry and says “only fix”
this post was submitted on 15 Sep 2023
994 points (98.8% liked)
Programmer Humor
32557 readers
313 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Makes me glad that I don't need to look at user reports.
"This bug happened"
"Ok, can you tell us the things you did to make it happen?"
"You're the developers, figure it out"
Unfortunately, sometimes they can't determine reproduction steps because it's rare to happen and required multiple things, or they just didn't catch it. I definitely don't blame them, at least not in a lot of cases.
And sometimes logs or crash dump or whatever is all you need to figure out the bug anyway. In fact, ideally it should be more often than not.
That's true. I work in QA, so I'm all too familiar with the experience of "wait, wtf just happened". I don't fault users in that situation. My problem is when it's "I crash every time on this level", without any explanation
I had a WFM role that involved me listening in on recordings and live calls to techs for a few years... Hell of an insight.
My end user reports are as efficiently descriptive as possible. Every time I have to submit something or contact, I aim to have their experience as pleasant as possible. I aim to be a 5-10 min break for them and am more than happy to talk shit with them as long as they want to delay their next interaction with Kevin or Karen.
I do the same thing, and it pays off. Afew months ago, my Dell computer was being really laggy. I had a maintenance contract, and when I called them, I gave them a detailed description of the behavior and a list of exactly what I had tried before calling (it was extensive and exhaustive). I could hear the gears in the support repository head grind to a half momentarily and then restart in another mode altogether, and she jumped right to advanced troubleshooting. It was a great moment for both of us,.
Must be nice working at a place where that ticket doesn’t just get dropped into the dev backlog as-is.
This person supports.
'Link to public issue tracker'
Report there.