<^> Top 10 replies by programmers, when their codes don't work <^>

Question

0. It works on my machine.
1. Did you check for virus in your machine?
2. It must be a hardware problem.
3. It has never done that before.
4. How is that possible!
5. What did you type in wrong, to cause it to crash?
6. You can't use that version in your system.
7. I haven't touched that module in weeks.
8. I can't test everything.
9. Somebody must have changed my code.

<^> what reasons do you give or get? <^>

Answer 1

10. I put that bug on purpose! ^_^

Answer 2

I love how the list starts with 0

Answer 3

It's not a bug, it's a feature :-P

Answer 4

It's a self-termination feature to avoid harm on your system.

Answer 5

It needs funding.

Answer 6

first must check power supply 😂😂😂😂😂😂😂😝😝😝😝😝😝

Answer 7

I only use codes that are supported and I try my codes in different virtual machines before publishing ....so if its not a beta version , it will most likely work 😊

Answer 8

it needs some motivation for the initilization to kick in

Answer 9

My top reply: "Ok that's all for today"

Answer 10

10. I use xyz antivirus, install and scan your damn system...lol

Answer 11

I would think me as a great programmer if my program got to that stage. My program has so many bugs if i decode one 10 more comes.
Just For Fun.
Sir nice one as always and great replies.

Answer 12

PEBKAC: Problem Exists Between Keyboard And Chair

Answer 13

I agree with cheeze. Love the 0 indexed list lol

Answer 14

The best is :
It was intended to do that way.

Answer 15

sometime its okay to be wrong

Answer 16

It's not a bug, that's a new feature!

Answer 17

Cosmic rays flipped the check bit.

Answer 18

0 and 4 are my replies when my teacher ask

Answer 19

oops! give me just a sec to look into it......

Answer 20

me: dang it! why can't i get this code to work

computer: error message: ...you...are an..idiot

me: ? ... yeah that makes sense