The best debugging habit is leaving a clean trail

I’ve been thinking the habit that scales isn’t “be fast,” it’s “leave yourself a clean trail back to the bug.” When I come back to a weird issue the next day, the thing that saves me is usually a tiny repro, a note about what I already ruled out, or even just a screenshot of the broken state.

That feels way more durable than heroic memory. What do people here actually keep around so the next round of debugging doesn’t start from zero?

1 Like