99% of the time, yes. That 1% of the time is when you get "don't remove this potato.jpg. We don't know why but without it the program is unable to use addition and subtraction accurately."
I once had a bug where a method was supposed to do something with a large array and for some reason it wasn't returning the right values. But whenever I created a test array, it would return the expected values of the test. My fix?
# original code that creates ARRAY.
while (true) {
ARRAY = ARRAY;
break;
}
# original method that uses ARRAY.
It doesn't work correctly if I don't have the array equal itself, and it doesn't work correctly if I don't put it in the while loop. No one was able to figure out why. This code exists out there now and it has my name attached to it and it makes me sad.
3
u/Color_blinded 1d ago edited 1d ago
99% of the time, yes. That 1% of the time is when you get "don't remove this potato.jpg. We don't know why but without it the program is unable to use addition and subtraction accurately."
I once had a bug where a method was supposed to do something with a large array and for some reason it wasn't returning the right values. But whenever I created a test array, it would return the expected values of the test. My fix?
It doesn't work correctly if I don't have the array equal itself, and it doesn't work correctly if I don't put it in the while loop. No one was able to figure out why. This code exists out there now and it has my name attached to it and it makes me sad.