What the... what the hell?!
Oct. 26th, 2005 05:46 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
terryclothSeriously, I'm starting to think someone is going in and randomly changing my code under me just to see if they can drive me insane.
Yes, the bulk of the problems are happening because D checked in some changes which changed how things draw and which events we get when. But... there are things that really, really, never could have worked, but I know I tested them, and they did. And every little thing is going wrong -- everything. Every last little step of the demo script, which did nothing that I hadn't tested a dozen times before, goes wrong in more than one way.
And then I'll make a change to fix one of the problems, rerun the same test I just did, and something new will go wrong that is completely unrelated. So I go to fix that, and on the way to rerun the test, before I can get to that step, something *else* will go wrong! And these aren't random intermittent bugs, these are code defects which always should have failed, assuming the code was like that five minutes ago, and yet didn't.
It's getting to the point where I seriously don't expect the code to be the same each time I look at it, let alone run the same on each trial. The only way I can deal with this is to assume that I'm attempting to clumsily entangle a magical, malicious code-like entity which wants me to suffer.
Using chopsticks.
Yes, the bulk of the problems are happening because D checked in some changes which changed how things draw and which events we get when. But... there are things that really, really, never could have worked, but I know I tested them, and they did. And every little thing is going wrong -- everything. Every last little step of the demo script, which did nothing that I hadn't tested a dozen times before, goes wrong in more than one way.
And then I'll make a change to fix one of the problems, rerun the same test I just did, and something new will go wrong that is completely unrelated. So I go to fix that, and on the way to rerun the test, before I can get to that step, something *else* will go wrong! And these aren't random intermittent bugs, these are code defects which always should have failed, assuming the code was like that five minutes ago, and yet didn't.
It's getting to the point where I seriously don't expect the code to be the same each time I look at it, let alone run the same on each trial. The only way I can deal with this is to assume that I'm attempting to clumsily entangle a magical, malicious code-like entity which wants me to suffer.
Using chopsticks.
