I don’t know why my own base competency in not screwing up little details of the code is disappointing to me but I do like that quicktest tells you exactly where you screwed up and what’s wrong. There’s a rush you get from successfully locating and fixing the problem. So each time I run it and it comes up clean, I feel like that “hit” I get is missing, just a little.
Not really; there’s a satisfaction to busting bugs, but it pales next to the feeling of knowing no bugs remain to be busted and you can move on to something else. Time spent fixing code is time not spent writing, after all. Or spent playing Dream Quest.
I love it when quicktest or randomtest pass on the first go, especially if it’s been a while since I tested!
I think I feel the opposite. With me, no matter how carefully I code, there’s always at least five times a chapter where the quicktest will fail… And for some reason the line number it says has the problem is always slightly off, so I’ll have to look at all the lines slightly above and below that line to try and find where the problem is. Once I’ve finally found all the problems and the quicktest comes up clean, that’s when I get the little rush.
lol I hope you’re joking (or I want your outlook on life if you’re not.) I look at the errors and realise just how many coding mistakes I can make when I think there is none there (same with spelling mistakes ) Extra sad points when it’s a tricky error that takes ages to work out. I kind of get rather happy when it’s running though and finishes error free!
In my six years of writing interactive fiction and my hundreds of times running quicktest, I’ve probably passed it on my first go like ten times.
Egads, no. I am always incredibly relieved, lol.