awww sh!t.. This is why you don't procrastinate

LongCoolMother

Diamond Member
Sep 4, 2001
5,675
0
0
Our puzzle-solving project was due today and I just submitted it before midnight/deadline. Anyway, the program part of the project was done, and all that was left was the readme and some debugging options. Not hard right?

Well, I felt pretty confident, since the program is running great and I figured throwing in some debugging options and BSing a readme wouldn't be so hard. So I cut it close. Big mistake. Less time to work = no time to test.

After I submitted, it turned out the program ran perfectly as I had planned, but one of the debug options was screwed up. Its actually just a switch where you can turn on a timer and it times in how many second the program can solve the puzzle. I raised an eyebrow when both the easiest and the hardest puzzles both said the puzzle took "less than one second to solve."

The switch to start timing depends on a boolean, which I toggle when the user wants the timing option on. Problem is, the reassignment to that boolean comes after my timer's start method call. CRAP! So the timer never begins, because the program doesn't know to start timing! AGH! Such a stupid mistake. So easy to fix had I just started earlier and done some testing.


I'll consider it a lesson learned. -_-