Thread: Top 20 Replies by Programmers when their programs don't work View Single Post
OvI's Avatar
OvI
«¤» rYTµm «¤»
Posts/Threads: 4,516/494
Thanks: 183
Thanked 932 Times in 647 Posts
Nominated 0 Times in 0 Posts
TOTW/F/M Award(s): 0
Rep Power/Points: 551/42187
OvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond reputeOvI has a reputation beyond repute
Default Top 20 Replies by Programmers when their programs don't work, Posted February 17th, 2006, 12:08 AM #1 (permalink) |
Top 20 Replies by Programmers 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 works on my machine."

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

1. "It must be a hardware problem."






| Reply With Quote