I couldn’t tell if my bot was actually improving
I stopped guessing whether my bot was improving. The answer was never in the game I kept watching.
-
-
why I stopped reading the terminal
Why hello Reader, I spent way too long trying to get a Zealot to stand guard for my Zerg rush defense. He had one job: move into the correct location when an enemy appeared. But spending hours squinting at terminal logs, trying to juggle X and Y coordinates in my head just to figure out where he actually stood, was driving me nuts. I was in terminal hell. It’s a miserable way to build. When you try to debug pathing by reading a wall of text, you’re taking something that happens in space and…
-
I let AI code my bot without me
I let an AI iterate on my bot without babysitting. The key was what I added to it.
-
The day print betrayed me
Debug smarter: stop scrolling logs and start seeing your bot’s brain in action
-
Stop drowning in bug fixes
You know that feeling when you boot up a replay after noticing a loss, only to watch your bot flailing around, doing all sorts of weird things? By the time you’re done reviewing, there’s a mountain of fixes staring back at you—and honestly, it can feel overwhelming. Here’s the good news: you don’t need to fix everything, just the right things.
