Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Mr Skrunts]

There was this car that was driving very slowly down the highway. A State Trooper pulls it over. "What have I done wrong, officer?" the driver asks.
"You are going 26mph on a major highway. There is a law against that," the officer says to the driver. "You must go at least 50mph."
"But when I turned on the highway, the sign said 26!" the driver replies.
"HA HA HA!" The officer laughs out loud. "That is because this is Interstate 26! The 26 isn't the speed limit!"
The driver leans back in her car seat and the cop sees another woman sitting beside her. She looked as pale as a ghost.
"What happened to her?" the officer asks.
"I don't know, but she has been that way ever since we got off of interstate 160."

[Mr Skrunts]

A man in a Porsche 911 stops at a stoplight and a guy on a scooter pulls up next to him. The guy on the scooter leans over and takes an admiring look at the inside of the Porsche and tells the driver that he has a really hot car. Well, the light turned green so the driver of the Porsche decides to show off and peels out and leaves the guy on the scooter in the dust. Then, all of a sudden, he sees the scooter zip on past him. So, being a little cocky, the Porsche driver floors it again and blows past the guy on the scooter. A few seconds later, he again sees the scooter zip on past him. So now he's a little irate as well as a little mifted that that scooter keeps passing him so he floors it until he is going over 100 mph. He thinks to himself that there would be no way that scooter could catch him now, but then looks in the rearview mirror and sees that scooter starting to catch up. He then decides to find out what that scooter really is and slams on his brakes. Then the scooter crashes into the Porsche. After the dust settled, the Porsche driver sees the scooter driver lying in the road and goes over to him and askes how he could go as fast as the Porsche on a little wimpy scooter... The dying man replied, "I can't really, but my suspenders were caught on your side mirror...."

[Mr Skrunts]

A traffic cop flagged down a motorist and said, 'I'm arresting you for going through three red lights.'
'Yeah, well, I'm colour blind,' said the motorist.
'In addition to that, you were exceeding the speed limit,' said the policeman. 'So what?' said the motorist. 'And on top of all that you were going the wrong way down a one-way street,' added the officer. 'I always did have a lousy sense of direction,' said the motorist with a smile.
At that point, his wife leaned forward from the ,back seat and said, 'Don't pay any attention to him, officer. He always talks like this when he's had a few drinks.'

[Mr Skrunts]

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.

[rickyboy]

Liked them all...  

[Mr Skrunts]

Wife: "There's trouble with the car. It has water in the carburetor."
Husband: "Water in the carburetor? That's ridiculous."
Wife: "I tell you the car has water in the carburetor."
Husband: "You don't even know what a carburetor is. Where's the car?"
Wife: "In the swimming pool."

[Mr Skrunts]

A young lady was driving through a built-up area at about 70 mph when she noticed a motorcycle policeman on her tail. She increased her speed to 80 mph but the cop hung grimly on her tail. She put her foot down and pushed the car up to 90, drawing rapidly away from her pursuer. Suddenly she saw a garage up ahead and with a squeal of brakes she pulled up in the forecourt and dashed into the ladies' toilet. Five minutes later she emerged to find the motor-cycle policeman waiting for her. With a sweet smile she said, 'I bet you thought I'd never make it in time.'

[Mr Skrunts]

Magistrate: 'But if you saw the lady driving towards you, why didn't you give her half the road?'
Motorist: 'I was going to, Your Honour, as soon as I could find out which half she wanted.'

[jereboam]

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.

 

If only it was that easy!