Top 22 repliesIn IT by Programmers to Testers when their programs don't work:
This is when i conducted a survey in my office itself.And some points i got through mails.Its was really funny.have fun with IT its not always serious
The Reasons are as follows
22. It’s the functionality
21. It’s a known Issue
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.............
Come on, even u say it ......
Guess.............
"It works on my machine"
Do tell what you think about it
If you enjoyed this post Subscribe to the Free ItBusinessAnalyis Newsletter or Feed It through RSS Feed it to your home page .Leave a comment to this post tell what you think about the post and interact with author and fellow readers.
The Reasons are as follows
22. It’s the functionality
21. It’s a known Issue
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.............
Come on, even u say it ......
Guess.............
"It works on my machine"
Do tell what you think about it
If you enjoyed this post Subscribe to the Free ItBusinessAnalyis Newsletter or Feed It through RSS Feed it to your home page .Leave a comment to this post tell what you think about the post and interact with author and fellow readers.










