Jeff;

Your post is just what I need to put a smile on my face. A great way to start the week!

Here is a true story about a developer I knew and one of his clients. I was visiting the developer at the time of this conservation and the speaker phone was on.

1. Developer: Receives telephone call from client.
2. Client: The new application causes my system to crash.
3. Developer: Can you give me some details?
4. Client: I was using the program and hit the Ctl F1 keys at the same time and the screen went blue!
5. Developer: Long pause --- “You should never hit that combination of keys”!

A feature is a feature – sometimes we differ as to what all this means!

Tom


>You are joking, right Ken?
>
>I wonder what genius at MS came up with that one - sounds like something Steve Ballmer would state in a company-wide email.
>
>The concept is as absurd as the following scenario:
>
>Developer delivers app to customer. Customer comes back to developer:
>
>Customer: “The trial balance report crashes as well as the remote check printing.”
>
>Developer: “You didn’t say you didn’t want it to crash.”
>
>Customer: “It goes without saying.”
>
>Developer: “It is not specified in your requirements. The non-crash feature will take an additional 200 hours for the trial balance report and 300 hours for remote check printing.”
>
>Customer: “Are you kidding?”
>
>Developer: “Absolutely not. We consider this a feature.”
>
>Customer: “We’ll see about that!”
>
>Developer (anticipating a problem) employs John Peterson to frustrate and confuse the customer.