Prone Jokes / Recent Jokes

Q: Why is Clinton prone to losing his voice? A: He keeps having to eat his words.

The following is a confidential report on several candidates being considered for a pastorate:
Adam: Good man but problems with his wife. Also one reference told of how he and his wife enjoy walking nude in the woods.
Noah: Former pastorate of 120 years with not even one convert. Prone to unrealistic building projects.
Abraham: Though the references reported wife-swapping, the facts seem to show he never slept with another man's wife, but did offer to share his own wife with another man.
Joseph: A big thinker, but a braggart, believes in dream-interpreting, and has a prison record.
Moses: A modest and meek man, but poor communicator, even stuttering at times. Sometimes blows his stack and acts rashly. Some say he left an earlier church over a murder charge.
David: The most promising leader of all until we discovered the affair he had with his neighbor's wife.
Solomon: Great preacher but our parsonage would never hold all those wives.
Elijah: more...

1. Thou shalt not worry about bugs.
Bugs in your software are actually special features.
2. Thou shalt not fix abort conditions.
Your user has a better chance of winning state lottery than getting the same abort again.
3. Thou shalt not handle errors.
Error handing was meant for error prone people, neither you or your users are error prone.
4. Thou shalt not restrict users.
Don’t do any editing, let the user input anything, anywhere, anytime. That is being very user friendly.
5. Thou shalt not optimize.
Your user are very thankful to get the information, they don’t worry about speed and efficiency.
6. Thou shalt not provide help.
If your users can not figure out themselves how to use your software than they are too dumb to deserve the benefits of your software any way.
7. Thou shalt not document.
Documentation only comes in handy for making future modifications. You made the software perfect the first time, it will more...

Thou shalt not worry about bugs.
Bugs in your software are actually special features.
Thou shalt not fix abort conditions.
Your user has a better chance of winning state lottery than getting the same abort again.
Thou shalt not handle errors.
Error handing was meant for error prone people, neither you or your users are error prone.
Thou shalt not restrict users.
Don't do any editing, let the user input anything, anywhere, anytime. That is being very user friendly.
Thou shalt not optimize.
Your users are very thankful to get the information, they don't worry about speed and efficiency.
Thou shalt not provide help.
If your users can not figure out themselves how to use your software than they are too dumb to deserve the benefits of your software anyway.
Thou shalt not document.
Documentation only comes in handy for making future modifications. You made the software perfect the first time, it will never need more...