I keep finding that the part that scales isn’t raw troubleshooting speed, it’s whether you leave behind enough of the trail to make the next pass less stupid. Once a bug has bounced through a few people, memory gets fuzzy fast and the story turns into folklore.
Do people here keep a real debugging log or checklist, or is that just me being annoyingly organised?
i keep a little debug note in the ticket too, mostly because otherwise it turns into “i swear we already tried that” theater.
the stuff that actually helps later is the boring bits: what you tried and ruled out, plus the exact repro steps / env / browser / whatever. future me is always way dumber than present me, so i try to leave a trail he can follow without guessing.
I don’t keep a formal debugging log, but I do leave a trail on purpose because otherwise it turns into vibes.
The part that keeps paying off is writing down what I ruled out and why, with the exact inputs and versions. “We tried that” is basically useless without the conditions.
I usually put the notes right in the ticket, then dump the messier stuff in my own notes if it gets long. Do you keep yours in the issue itself, or somewhere separate?
:: Copyright KIRUPA 2024 //--