Top 20 replies by programmers when their programs do not work

Subject: Top 20 replies by programmers when their programs do not work
From: Sona Mehta <sona -dot- mehta -at- haysmt -dot- co -dot- uk>
To: "'techwr-l -at- lists -dot- raycomm -dot- com'" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Mon, 19 Jun 2000 13:54:46 +0100

Here is something I could not resist sharing with you guys.

Top 20 replies by programmers when their programs do not work

20. "That's weird..."
19. "It's never done that before."
18. "It worked yesterday."
17. "How is that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it hasn't been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"

And the Number One Reply by Programmers when their programs don't work:

1. "It works on my machine."





Previous by Author: Help in Planning
Next by Author: Checking for technical accuracy
Previous by Thread: Summary User Names
Next by Thread: Re: Top 20 replies by programmers when their programs do not work


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads