Tech Support:Nietzsche Style

Drakon

I got a rock.
Joined
Jul 26, 2003
Messages
28,238
Reaction score
0
Points
56
When a user is calling in need of help, don't forget that he is a weakling. Only a loser would need to come groveling to you, begging for crumbs of help that may fall from your godlike lips. And he knows that he is a loser in the race of the weak and the strong, that his kind is doomed to extinction. Therefore, show him no mercy. Treat him with the utter contempt that he deserves. It is the law of nature that you should do so.

Key Phrases:

"You aren't very smart, are you?"
"I can't believe you call yourself a programmer!"
"Our product is obviously too complex and advanced for you. Please desist from using it -- you are soiling it."

Nevertheless, there may come a time when you actually must help the user, even though he is sucking away your magnificent intellectual vitality with his grotesque shambling confusion. He is a lower form of life and you must make him feel it, lest he take on ambitions of evolving to your level.

Key Phrases:

"Now I will read aloud the section of the manual that you failed to comprehend."
"You have ignominiously blundered on line 35, committing an error that a Mongoloid programming an abacus would be ashamed of."
"What you've done in your function foo is the coding equivalent of failing to empty your colostomy bag."

Alas, upon occasion there comes a time when it is obvious that the compiler is at fault. This is no reason to let the user feel superior to anyone, however. The design of a compiler is still far beyond his limited mental capacities. His duty is to worship, not criticize.

Key Phrases:

"The inner workings of the compiler are far beyond your antlike comprehension."
"That behavior is described in ANSI specification 21.11.45.7.3.8. You are familiar with that section, I assume..."
"Our software can behave in that manner only if it has been corrupted by long exposure to users of your caliber."

And finally, a user may eventually want you to code something for him, or send him an example. The user has asked something that is against the laws of nature. Such creatures as himself exist to serve you and not you him. Therefore such a request is impossible and against nature, and does not exist, and therefore never happened. Response is not possible.
----------------------------------------------------

I figured two of you would get a kick out of then, and in about thirty minutes this thread shall also fall into obscurity.
 
I'll remember this thread the next time you IM me for technical help, Drak. :D

jag
 
Awww. :(

This also reminds me of my favourite line from "The Producers:The Musical"

"So, Jason. What have you been up to?"
"For the last sixteen years, I have been touring in 'No No Nietzsche' "
"You played Nietzsche?"
"No No."
 
Some of those phrases should be incorporated into my everyday lexicon. :D

And people have the nerve to say that programmers are self-deluded arrogant pricks. :rolleyes:
 
I think it has to do with answering the same problem over and over and over again, when the answer is so incredibly simple.

"My PC won't turn on"
"Is it plugged in?"
"Of course it is!"
"Does it flicker on at all, even for a split second, or is it completely not turning on?"
"It won't turn on!"
"I'm aware of that sir, but this troubleshooting helps me better find the--"
"Look, you're an idiot. Lemme talk to your boss"
--
"Hello, this is the supervisor."
"That last guy was an idiot, can you help me?"
"What seems to be the problem?"
"My PC won't turn on"
"Is it plugged in?"
"Of course it is! I told you already"
"No, sir, I didn't know that"
"I told the other guy, he shoulda told you!"
"Well, he didn't. So, it's plugged in. Is the machine getting ANY power at all, or does it stay dead?"
"Oh, wait. The power cord wasn't plugged in. Nevermind. *click*
"And people wonder why there's a higher murder rate now than twenty years ago."
 

Users who are viewing this thread

Back
Top
monitoring_string = "afb8e5d7348ab9e99f73cba908f10802"