There’s a certain subset of techies who think because they speak a certain language, everyone else must. And that everyone else has the tools they have and know how to use them.
I point out and give screen shots of an issue that I’m told doesn’t exist and then they say, oh yeah… I can replicate that — you should approach it with XYZ. And then give incorrect links and useless information on top of jargon that means nothing to your average joe. And then there is the feel of “don’t call us, we’ll call you…maybe.” Actually, I know just enough to be dangerous and it was all babble to me. Imagine if a person seeing support was unfamiliar with these kinds of things? Absurd.
And you call yourself a “happiness engineer”?
This is why I dislike trying to help those kinds of people fix their bugs and why I would rather just vent.
This is after someone admitted there was a bug that was in the code that is no longer optional to roll back and beyond my ability to fix. Then they kept telling me to go back to the old code option. Only after I show them it is not an option anymore do they then throw gooply-gop at me that is supposed to temporarily fix it. Which, if I had the setup they have, might have worked [I openly doubt it, though]. But I don’t have that kind of access and I’m not interested in opening up that kind of security hole on my site. The icing is when they referenced the page on how to use the bugged part of the effin plugin as if THAT is the fix? Really? Are you trolling me?
Gemini fixed helped me temporarily “roll it back”, not in over a week, but in less than 15 minutes with a handful of meaningful instructions. And without the technobabble blow-off.
Seriously, this is the kind of crap is the reason helpdesk people have a reputation for being the helplessdesk people. It happens enough that this is the expected norm and why people cringe when they need to call or email support.
/rant
Leave a comment. Markdown permitted.