Quantcast
Channel: Vijay For Victory » Programming
Viewing all articles
Browse latest Browse all 4

Programmer’s reaction on a bug

$
0
0

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?


Viewing all articles
Browse latest Browse all 4

Latest Images

Trending Articles





Latest Images