Going Code Blind

Finding and fixing bugs is a part of programming, and some bugs are very troublesome to find the root of their cause. Often times I find myself discovering a bug and searching for hours to find out what's causing it only to find out it was a simple typo somewhere in my code or a node connected to the wrong thing in blueprints. After staring at your work for a while you tend to miss the simplest mistakes and go "Code Blind".

Sure enough, when I added additional challenges, a bug popped up right before a build submission that caused them not to track weapon kills. I went pasted code freeze trying to figure out the cause but to no avail. The following weekend I requested help from a friend and within a few seconds, he immediately noticed the issue I went blind too. It was a simple logic error where I was incorrectly using the .contains() function to check weapon names. Moments like that remind me to ask for help if you are having trouble finding issues in your code after staring at it for a while.