You’re terminal and your debug log text is getting extremely bloated. Some of your print statements have found their way into some nested recursive loops and your DebugLog.log file is reaching into the tens of hundreds of megabytes. There’s still no end in site but you feel closer as you are still able to trace your debug statements and miraculously find some print statements which should be showing up but are not. What do you do?
You never thought you’d ever use so many print statements!
Published by B McGraw
B McGraw has lived a long and successful professional life as a software developer and researcher. After completing his BS in spaghetti coding at the department of the dark arts at Cranberry Lemon in 2005 he wasted no time in getting a masters in debugging by print statement in 2008 and obtaining his PhD with research in screwing up repos on Github in 2014. That's when he could finally get paid. In 2018 B McGraw finally made the big step of defaulting on his student loans and began advancing his career by adding his name on other people's research papers after finding one grammatical mistake in the Peer Review process. View more posts