At Work — worst jokes

Random joke from this category

The Foot Pedal

An exasperated caller to Tech Support couldn't get her new computer to turn on. After ensuring the computer was plugged in, the technician asked her what happened when she pushed the power button. Her response "I pushed and pushed on this foot pedal and nothing happens."

The "foot pedal" turned out to be the computer's mouse.

Unplug The Power Cord

An office technician got a call from a user. The user told the tech that her computer was not working. She described the problem and the tech concluded that the computer needed to be brought in and serviced.

He told her to "Unplug the power cord and bring it up here and I will fix it."

About fifteen minutes later she shows up at his door with the power cord in her hand.

Brakes Failed on the Mountain

A Software Engineer, a Hardware Engineer and a Branch Manager were on their way to a meeting. They were driving down a steep mountain road when suddenly the brakes on their car failed. The car careened almost out of control down the road, bouncing off the crash barriers, until it miraculously ground to a halt scraping along the mountainside.
The car's occupants, shaken but unhurt, now had a problem: they were stuck halfway down a mountain in a car with no brakes. What were they to do?

"I know," said the Branch Manager, "Let's have a meeting, propose a Vision, formulate a Mission Statement, define some Goals, and by a process of Continuous Improvement find a solution to the Critical Problems, and we can be on our way."

"No, no," said the Hardware Engineer, "That will take far too long, and besides, that method has never worked before. I've got my Swiss Army knife with me, and in no time at all I can strip down the car's braking system, isolate the fault, fix it, and we can be on our way."

"Well," said the Software Engineer, "Before we do anything, I think we should push the car back up the road and see if it happens again."

Programmer Excuses

Comments made by Programmers when their programs don't work:

  • Strange...
  • I've never heard about that.
  • It did work yesterday.
  • Well, the program needs some fixing.
  • How is this possible?
  • The machine seems to be broken.
  • Has the operating system been updated?
  • The user has made an error again.
  • There is something wrong in your test data.
  • I have not touched that module!
  • Yes yes, it will be ready in time.
  • You must have the wrong executable.
  • Oh, it's just a feature.
  • I'm almost ready.
  • Of course, I just have to do these small fixes.
  • It will be done in no time at all.
  • It's just some unlucky coincidence.
  • I can't test everything!
  • THIS can't do THAT.
  • Didn't I fix it already?
  • It's already there, but it has not been tested.
  • It works, but it's not been tested.
  • Somebody must have changed my code.
  • There must be a virus in the application software.
  • Even though it does not work, how does it feel?
  • How come you didn't find it during the system testing?
  • It's a setup problem.

And the Ultimate:
A smart user would never do that!

Engineer Versus Programmer

A Engineer and an Programmer are sitting next to each other on a long flight from LA to NY. The Engineer leans over to the Programmer and asks if he would like to play a fun game.
The Programmer just wants to take a nap, so he politely declines and rolls over to the window to catch a few winks.

The Engineer persists and explains that the game is real easy and a lot of fun. He explains "I ask you a question, and if you don't know the answer, you pay me $5. Then you ask me a question, and if I don't know the answer, I'll pay you $5."

Again, the Programmer politely declines and tries to get to sleep.

The Engineer, now somewhat agitated, says, "OK, if you don't know the answer you pay me $5, and if I don't know the answer, I'll pay you $50!"

This catches the Programmer's attention, and he sees no end to this torment unless he plays, so he agrees to the game. The Engineer asks the first question: "What's the distance from the earth to the moon?"

The Programmer doesn't say a word, but reaches into his wallet, pulls out a five dollar bill and hands it to the Engineer.

Now, it's the Programmer's turn. He asks the Engineer "What goes up a hill with three legs, and comes down on four?"

The Engineer looks up at him with a puzzled look. He takes out his laptop computer and searches all of his references. He taps into the Airphone with his modem and searches the net and the Library of Congress.

Frustrated, he sends e-mail to his co-workers -- all to no avail.

After about an hour, he wakes the Programmer and hands him $50. The Programmer politely takes the $50 and turns away to try to get back to sleep.

The Engineer, more than a little miffed, shakes the Programmer and asks "Well, so what's the answer?"

Without a word, the Programmer reaches into his wallet, hands the Engineer a $5 bill, and turns away to get back to sleep.

The ID Ten T Error

Young Judy, the editor of a trivia publication, was having trouble with her computer. So she called Prem, the computer guy, over to her desk. Prem clicked a couple buttons and solved the problem.

As he was walking away, Judy called after him, "So, what was wrong?"

And he replied, "It was an ID ten T error."

A puzzled expression ran riot over Judy's face. "An ID ten T error? What's that ... in case I need to fix it again??"

He gave her a grin... ;-)

"Haven't you ever heard of an ID ten T error before?"

"No," replied Judy.

"Write it down," he said, "and I think you'll figure it out."

(She wrote...)

I D 1 0 T

Microsoft Support Light Bulb

How many Microsoft support staff does it take to change a light bulb?
→ Four. One to ask "What is the registration number of the light bulb?", one to ask "Have you tried rebooting it?", another to ask "Have you tried reinstalling it?" and the last one to say "It must be your hardware because the light bulb in our office works fine..."

Y to K Dates

Dear Boss, I hope I haven't misunderstood your instructions. Because to be honest, boss, none of this Y to K dates problem makes any sense to me.

At any rate I have finished converting all the months on all the company calendars so that the year 2000 is ready to go with the following improved months:
Januark, Februark, Mak, Julk.

In addition, I have changed the days of the week, and they are now:
Sundak, Mondak, Tuesdak, Wednesdak, Thursdak, Fridak and Saturdak.

Is it enough, or should I change any other Y to K? I am a fan of the New York Yankees. Should I call them New Kork Kankees in order to be Y2K ready?

The Great Writer

There was once a young man who, in his youth, professed his desire to become a great writer.

When asked to define "great" he said, "I want to write stuff that the whole world will read, stuff that people will react to on a truly emotional level, stuff that will make them scream, cry, howl in pain and anger!"

He now works for Microsoft, writing error messages.