You stare deep into the Abyss and the Abyss Stares back

close up photo of matrix background

From the lowest function to the highest config value, you read the code line by line…Until at last you threw down your keyboard, mouse, and smote the code’s ruin upon the mountain side…you read it all…Darkness overtakes you, and you stray out of thought and time…The stars wheeled overhead, and every day was as long as a life age of the earth…But it was not the end. You suddenly feel life again and realize that you have yet to find the bug. What do you do?

  1. Continue reading line by line
  2. Google the Error
  3. Strategically add a bunch of debug logging print statements
  4. Ask the guy who wrote the code
  5. Try running the code again

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: