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 - Applications, Java Platform, 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
Reading List - 05-Mar-23
Talking to #AI may be the most important job skill of this century ( JohnGoodPasture ) Role of account management over the years. It’s a ro...
-
Bugzilla is the Bugs/Issues Tracking Tool from The Mozilla Organization. Version 2.18 is the latest stable release. There are couple of res...
-
Two MIT math graduates bump into each other at Fairway on the upper west side. They hadn't seen each other in over 20 years. The first g...
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