Programmer's Excuses

A colleague sent me this today. I'm sure I've used almost all of them at some point!

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."

I've never really been into the whole 'random stream of conciousness' thing, but thought I'd start a blog and see what happens. Hey, everyone's doing it now, right? Is that the bandwagon I hear coming...

Don't expect miracles, I'm not very good at this sort of thing, but I plan to post anything that I find vaguely interesting. You never know, it might be useful to you, or at least make you chuckle/think.