Programmer’s reaction on a bug

October 22nd, 2009 Leave a comment Go to comments

When I was going through my mail box, I found this forward mail which I received long back.

This mail is about the programmer’s reaction when something is not working. The list gave me a smile.

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. OR It’s a data problem, not a program problem.
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 thing all Programmers say when their programs don’t work:

1. It works on my machine.

I too made a few comments that are in the above list :)

How about you?


Like this article?

  1. October 22nd, 2009 at 15:38 | #1

    hahaha.. pukka… I have got 16 of these response so far in my career!! Nice collection..

  2. October 22nd, 2009 at 19:59 | #2

    I hope those 16 are given by me to you :)

  3. October 25th, 2009 at 06:58 | #3

    I use to make these statements :) . But these days I hear them from my team members..

  4. March 15th, 2010 at 12:58 | #4

    Vijay, One more new comment added by my team member “Run the baseline and check if it works in that” :)

  5. March 15th, 2010 at 15:18 | #5

    @Anantha Ramakrishnan It is quite logical.

  1. No trackbacks yet.