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:
Guess.............
Guess..............
Guess.............
"It works on my machine" :)
Blog on things around me - Quality Management, Free & Open Source Software, Gadgets, Utilities...
Thursday, September 22, 2005
Programmers to Testers
Top 20 replies by Programmers to Testers when their programs don't work:
Subscribe to:
Post Comments (Atom)
Total Pageviews
395,373
Popular Posts
-
" Is you primary platform Microsoft based? Do you work with Microsoft products most of the time? Are most of your Google Searches Micro...
-
I tried reaching Google Adsense via google.com/adsense in Google Chrome, and I was prompted with the this message :) Amazon.com Get Technica...
-
Always give your 100% to work... :) [received in an email]
-
life in balance : life in balance Add me on Twitter! Come follow my daily antics, links, tips and more @rajneeshgarg on Twitter!
-
A highly useful guide on software pricing by Neil Davidson is available as e-book on author's website . A printed copy can be purchased ...
4 comments:
Funny. I can relate to these 110%.
"It works on my machine"
I knew it! It's so true. So sad, but so true.
But it compiled just fine!
Quantum indeterminacy makes software unpredictable.
Post a Comment