Code Jokes / Recent Jokes

Jokes Difference between boys and girls while using ATM (Bank's cash dispenser machines) Boys: 1. Drive to the bank, park and go to the Cash Dispenser. 2. Insert card 3. Dial code and desired amount 4. Take the cash, the card and the slip Girls: 1. Drive to the bank 2. Engine stalled 3. Check make-up in the mirror 4. Apply perfume 5. Manually check haircut 6. Park the car - failure 7. Park the car - failure 8. Park the car - Success 9. Search for the card in the handbag 10. Insert card, rejected by the machine 11. Throw phone card back in handbag, 12. Look for bank card. 13. Insert Card 14. Look for Secret Box (where secret code is written)in Handbag 15. Enter code 16. Study instructions for 2 minutes 17. #Cancel# 18. Re-enter code 19. #Cancel# 20. Call Boyfriend/husband to get correct the code 21. Enter desired amount 22. #Error# 23. Enter bigger amount 24. #Error# 25. Enter maximum amount 26. Cross fingers 27. Take cash 28. Go back to the car 29. Check make up in rear mirror 30. more...

TO: ALL PERSONNELFROM: ACCOUNTING It has come to our attention recently that many of you have been turning in timesheets that specify large amounts of "Miscellaneous Unproductive Time" (Code 5309). However, we need to know exactly what you are doing during your unproductive time. Attached below is a sheet specifying a tentative extended job code list based on our observations of employee activities. The list will allow you to specify with a fair amount of precision what you are doing during your unproductive time. Please begin using this job-code list immediately and let us know about any difficulties you encounter. Thank you, AccountingAttached: Extended Job-Code ListCode and Explanation5316 Useless Meeting5317 Obstructing Communications at Meeting5318 Trying to Sound Knowledgeable While in Meeting5319 Waiting for Break5320 Waiting for Lunch5321 Waiting for End of Day5322 Vicious Verbal Attacks Directed at Coworker5323 Vicious Verbal Attacks Directed at Coworker While more...

Programmer produces code he believes is bug-free.
Product is tested. 20 bugs are found.
Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
Repeat three times steps 3 and 4.
Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
Users find 137 new bugs.
Original programmer, having cashed his royalty check, is nowhere to be found.
Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
Original programmer sends underpaid testing department a postcard from Fiji.
Entire testing department quits.
Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
New CEO is brought in by board of directors. He more...

99 little bugs in the code,
99 bugs in the code,
fix one bug, compile it again,
101 little bugs in the code.
101 little bugs in the code,.... > (Repeat until BUGS = 0)

There was an old priest who got sick of all the people in his parish who kept confessing adultery. One Sunday, from the pulpit, he said, "If I hear one more person confess to adultery, I'll quit!" Well, everyone liked him, so they came up with a code word. Someone who had committed adultery would say they had "fallen." This seemed to satisfy the old priest and things went well, until the priest died at a ripe old age.

About a week after the new priest arrived, he visited the Mayor of the town and seemed very concerned. The priest said, "You have to do something about the sidewalks in town. When people come to the confessional, they keep talking about having' fallen.'"

The Mayor started to laugh, realizing that no one had told the new priest about the code word. Before the mayor could explain, the priest shook an accusing finger at the mayor and said, "I don't know what you're laughing about! Your wife fell three times this more...

The Life Cycle of Software

Programmer produces code he believes is bug-free. Product is tested. 20 bugs are found. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs. Testing department finds that five of the fixes didn't work and discovers 15 new bugs. See 3. See 4. See 5. See 6. See 7. See 8. Due to marketing pressure and an extremely pre-mature product announcement based on over-optimistic programming schedule, the product is released. Users find 137 new bugs. Original programmer, having cashed his royalty check, is nowhere to be found. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs. New CEO is brought in by board of directors. He hires programmer more...

A recent college graduate got hired by the human-development center of a large corporation to train the employees in proper dress code and etiquette.
One day as she was stepping onto the elevator, a man who was casually dressed in jeans and a golf shirt got on with her.
"Dressed a little casually today, aren't we?" she said in a scolding tone.
"That's one of the benefits of owning the company," the man replied with a grin.