Author Topic: Science / Computer Joke Thread  (Read 2236 times)

These are some of my favorite programming jokes, please enjoy!
(Sorry if you don't get some of 'em!)

--- -

“Knock, knock.”

“Who’s there?”

very long pause….

“Java.”

--- -

   
A physicist, an engineer and a programmer were in a car driving over a steep alpine pass when the brakes failed. The car was getting faster and faster, they were struggling to get round the corners and once or twice only the feeble crash barrier saved them from crashing down the side of the mountain. They were sure they were all going to die, when suddenly they spotted an escape lane. They pulled into the escape lane, and came safely to a halt.

The physicist said "We need to model the friction in the brake pads and the resultant temperature rise, see if we can work out why they failed".

The engineer said "I think I've got a few spanners in the back. I'll take a look and see if I can work out what's wrong".

The programmer said "Why don't we get going again and see if it's reproducible?"

--- -

   
If you put a million monkeys at a million keyboards, one of them will eventually write a Java program.

The rest of them will write Perl programs.

--- -

["hip", "hip"]

(hip hip array!)

--- -

A Cobol programmer made so much money doing Y2K remediation that he was able to have himself cryogenically frozen when he died. One day in the future, he was unexpectedly resurrected.

When he asked why he was unfrozen, he was told:

"It's the year 9999 - and you know Cobol"

--- -

Q: How many prolog programmers does it take to change a lightbulb?

A: Yes.

--- -

Q: how many Microsoft programmers does it take to change a light bulb?

A: none, they just make darkness a standard and tell everyone it's a feature

--- -

Q: How many C++ programmers does it take to change a light bulb?

A: You’re still thinking procedurally. A properly designed light bulb object would inherit a change method from a generic light bulb class, so all you would have to do is call the light-bulb-change method.

--- -

To understand what recursion is, you must first understand recursion.

--- -

A guy is standing on the corner of the street smoking one cigarette after another. A lady walking by notices him and says
"Hey, don't you know that those things can kill you? I mean, didn't you see the giant warning on the box?!"
"That's OK" says the guy, puffing casually "I'm a computer programmer"
"So? What's that got to do with anything?"
"We don't care about warnings. We only care about errors."

--- -

So this programmer goes out on a date with a hot chick...

--- -

The fantastic element that explains the appeal of games to many developers is neither the fire-breathing monsters nor the milky-skinned, semi-clad sirens; it is the experience of carrying out a task from start to finish without any change in the user requirements.

--- -

A Geologist and an engineer are sitting next to each other on a long flight from LA to NY. The Geologist leans over to the Engineer and asks if he would like to play a fun game. The Engineer just wants to take a nap, so he politely declines and rolls over to the window to catch a few winks. The Geologist persists and explains that the game is real easy and a lotta 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 Engineer politely declines and tries to get to sleep. The Geologist 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 Engineer's attention, and he sees no end to this torment unless he plays, so he agrees to the game. The Geologist asks the first question. "What's the distance from the Earth to the moon?"

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

Now, it's the Engineer's turn. He asks the Geologist, "What goes up a hill with three legs, and comes down on four?" The Geologist 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 Engineer and hands him $50. The Engineer politely takes the $50 and turns away to try to get back to sleep.

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

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

--- -

I called the janitor the other day to see what he could do about my dingy linoleum floor. He said he would have been happy to loan me a polisher, but that he hadn't the slightest idea what he had done with it. I told him not to worry about it - that as a programmer it wasn't the first time I had experienced a buffer allocation failure due to a memory error.

--- -



The jokes are from here : http://stackoverflow.com/questions/234075/what-is-your-best-programmer-joke
The picture is from here : xkcd.com
« Last Edit: December 12, 2012, 02:48:32 PM by Supersolider »

what did the amd processor say to the intel processor

nothing because the intel processor was busy being used while the amd processor was sitting around

--- -

Q: how many Microsoft programmers does it take to change a light bulb?

A: none, they just make darkness a standard and tell everyone it's a feature

--- -

HAHAHAHA. This made my day.