Search This Blog

Mar 1, 2012

Common Replies of Programmers when their programs don't work

I smiled when I saw this post from chapagain's blog. Most of the reasons listed below are true and I often heard it. (To be honest, sometimes I used them too)? .
Here is the list of top 20 replies of Programmers when their program doesn'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?"
And the number One reply is:
1. "It works on my machine."


Mike said...

"It works on my machine" - I use this very often. Or should I say, "it works on my tablet" since I do apps for mobile devices. :))

Janz said...

haha very clever. :))