I keep coming back to this: the best debugging habit I’ve seen is just writing down the exact state before you touch anything. Not a clever trick, just enough context that you can come back two hours later and still know what changed.
I learned that the hard way on a CI issue that turned out to be a race condition between two tests sharing a port. Has anyone else found a habit that actually survives when the bug report gets handed to someone else?
