Debugging notes age better when they explain the pattern

i’ve been wondering if the best debugging habit is treating your notes like something another person will read later. Not just what you tried, but what the failure actually looked like and what pattern it belonged to.

when i look back at old bugs, the useful ones are always the ones where i wrote down the shape of the problem. do people here keep that kind of record, or does it turn into a pile of half-finished scraps like mine?