The Top 20 replies by programmers when their programs do not work:
Thursday, May 14, 2009 20:32The interesting fact about programmer / developer work when their program failed to run, mostly their replies will be following.
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:
1. "It works on my machine."
Fahad says:
June 9th, 2009 at 12:10 am
The post is awsome, I have seen these commonly used programmer replies during my development career life.
But about java there is Null Pointer Exception that every java programmer knows well, is missing.
Parshad says:
June 24th, 2009 at 2:23 pm
Your post is awsome about programmer’s replies, and I have enjoyed it very much. But Programmer are not always wrong, they are also innovative.
You should also highlight the positive key aspects of programmers.
anyways good post.