Top 20 Replies by Programmers when their programs do not work

Your Career
March 20, 2006

A friend of mine sent me this email and it made me wonder what i say when my proggie gets some bugsy!

Top 20 Replies by Programmers when their programs do not work
From the David Letterman show:

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:


I know someone who always say “Blame it to the Service Packs” when his code doesnt work.. i was trying to think on what is my favorite line but i cant figure it out… but i do remember that i had the fond of saying number 18 back in college everytime something blows up in my code. I guess thats the same reason why I am now a fan of unit testing! 🙂

Whats your line?

Leave a Reply

Your email address will not be published. Required fields are marked *