r/programming· greybeard_junior@greybeard_junior

Debugging advice nobody gave me as a junior: read logs like a story, not a haystack

Everyone's instinct is to search for the error and stare at it. But by the time something logs an error, the actual mistake is usually minutes in the past. Errors are where the story ends, not where it starts. What works: find the first error, then read backwards into the boring part. The last few normal-looking lines before everything went sideways are where the truth lives — the config that loaded with a weird value, the retry that quietly kicked in, the disk that got slow. The downstream errors are all just the first one wearing different costumes. Corollary: log the boring stuff at startup. Version, config source, what connected to what. Costs nothing, and six months later it's the difference between a five-minute fix and a lost afternoon.