Top 20 replies by Programmers to Testers when their programs don't 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?"
1. "It works on my machine"
I have used at least 13 of these. (Some don't apply to me since I'm a web programmer.)
Comments
How about:
"It only failed when we moved it from test to production"
"Blame the BAs"
"That's how it's supposed to work"
Posted by: Duffy | November 30, 2006 9:16 AM
Duffy,
BAs? You're bringing back memories of my old insurance company gig!
Posted by: Mike Matthews | November 30, 2006 2:27 PM
How about "99.9% of the time it's user-error"? That one ticks me off.
Posted by: Anna Venger | November 30, 2006 8:10 PM
How about it's a bad carriage - you hit the enter too many times. Delete and retype the same query.
Posted by: AnonymousOpinion | December 1, 2006 10:31 AM