Thread

Time to stop arguing… tell some jokes!

“Have you heard about the object-oriented way to become wealthy?”
“No…”
“Inheritance.”

Hi Libbi,

I like your joke and surprised that no one else has responded to this thread.

Here’s an old one that I once thought was funny. I have now changed my mind and think that there is more than just a grain of truth in the joke:)

A man was crossing a road one day when a frog called out to him and said, “If you kiss me, I’ll turn into a beautiful princess.” He bent over, picked up the frog, and put it in his pocket.

The frog spoke up again and said, “If you kiss me and turn me back into a beautiful princess, I will tell everyone how smart and brave you are and how you are my hero.”

The man took the frog out of his pocket, smiled at it, and returned it to his pocket.

The frog spoke up again and said, “If you kiss me and turn me back into a beautiful princess, I will be your loving companion for an entire week.”

The man took the frog out of his pocket, smiled at it, and returned it to his pocket.

The frog then cried out, “If you kiss me and turn me back into a princess, I’ll stay with you for a year and do ANYTHING you want.”

Again the man took the frog out, smiled at it, and put it back into his pocket.

Finally, the frog asked, “What is the matter? I’ve told you I’m a beautiful princess, that I’ll stay with you for a year and do anything you want. Why won’t you kiss me?”

The man said, “Look, I’m a computer programmer. I don’t have time for a girlfriend, but a talking frog is cool.”

 

 
Cheers & have a happy weekend,

John_Betong
 
 

I like the joke about the frog and the first one was nice I copied and pasted this joke from http://www.computerjokes.net/063.htm

I guess all jokes are copied and pasted from some where.

The Software Development Cycle

Software doesn’t just appear on the shelves by magic. That program shrink-wrapped inside the box along with the indecipherable manual and 12-paragraph disclaimer notice actually came to you by way of an elaborate path, through the most rigid quality control on the planet. Here, shared for the first time with the general public, are the inside details of the program development cycle.

  1.

    Programmer produces code he believes is bug-free.
  2.

    Product is tested. 20 bugs are found.
  3.

    Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.
  4.

    Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.
  5.

    See 3.
  6.

    See 4.
  7.

    See 5.
  8.

    See 6.
  9.

    See 7.
  10.

    See 8.
  11.

    Due to marketing pressure and an extremely premature product announcement based on an overly optimistic programming schedule, the product is released.
  12.

    Users find 137 new bugs.
  13.

    Original programmer, having cashed his royalty check, is nowhere to be found.
  14.

    Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
  15.

    Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
  16.

    Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
  17.

    New CEO is brought in by board of directors. He hires programmer to redo program from scratch.
  18.

    Programmer produces code he believes is bug-free.

The definition of an upgrade: Take old bugs out, put new ones in.