12
The guy at the library who explained why my code kept breaking
He saw me stuck on a loop error for 45 minutes and just said 'you're testing the input, not the output, check line 12,' and now I always print my variables before I blame the compiler, has anyone else had that one tiny hint that fixed everything for them?
1 comments
Log in to join the discussion
Log In1 Comment
alice9281d ago
Shook my whole world when you said library guy. Mine was a coworker who watched me chase a null pointer bug for two days. He finally looked over my shoulder and goes "you forgot to close the file handle on line 40, mate." I had been printing every single variable in three different functions. File handle. That was it. I still think about that moment every time I blame the environment instead of my own sloppy cleanup. It's wild how one tiny detail just rewires your whole approach to debugging.
6