You cuss at Game Maker for having no mechanism for stepping through your code when something goes horrifically wrong with a script containing multiple layers of nested loops.
AND OH WAIT I THINK I KNOW WHAT’S WRONG HANG ON
(this is what the blog is for)
ETA: HAHAHAHA YES I am in charge of A* pathfinding!
“what the blog is for” = getting my brain into critical mode and out of “my code isn’t wrong yours is” mode. See, that’s why I mostly only post about books I didn’t like! It’s not just because I’m a jerk!
In general, it is not constructive when I convince myself that my code is perfect and there is clearly something wrong with the interpreter/compiler. I am sure that people have existed who have found that there was a bug in the interpreter/compiler, which just happened to affect the long piece of code they’d written in one inspired sprint without any testing. However, given my habits, the odds that that will be the source of my problems are not high.