You go print statement happy!

person wearing silver framed eyeglasses

You look at all of the major functions in which the code may or may not be breaking. It starts to feel like a little over kill but it’s managable each run. You look through the outputs and in one place where you would be expecting a ‘Made it 17’ it just stops at ‘Made it 16’. It just stops there. What do you do?

  1. There are too many print statements, I’m feeling suffocated. Revert back
  2. Add more print statements around ‘Made it 17’ It has to be there!

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.

Leave a Reply

%d bloggers like this: