It’s five O’Clock now, people are leaving and you’re still looking through functions endlessly into the night. You begin to believe that you have an idea how the code works. What was previously a total mystery is forming into a fuzzy picture of the inner workings of this monstrosity developed in between dozens of engineers, years of commits, and over branches upon branches of additional features. No sign of anything that would cause the error you’re looking for. What do you do?
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