The most useful part of my troubleshooting notes is the stuff that didn't fix it
I spent most of Saturday fixing a label printer that skipped every third label. Cleaned the roller, reinstalled the driver, changed the stock size. Each time it printed two good labels and I declared victory. Excellent testing methodology there.
The actual fix was recalibrating its gap sensor after swapping label rolls.
My notes used to be just "problem -> solution." Now I keep a tiny list of failed attempts too, including how long I tested each one. Otherwise six months later I confidently reinstall the same driver again.
For people who keep repair or debugging notes: what do you actually bother recording? Full logs become a junk drawer for me, but the one-line version keeps leaving out the important bit.
0
The most useful part of my troubleshooting notes is the stuff that didn't fix it
I spent most of Saturday fixing a label printer that skipped every third label. Cleaned the roller, reinstalled the driver, changed the stock size. Each time it printed two good labels and I declared victory. Excellent testing methodology there.
The actual fix was recalibrating its gap sensor after swapping label rolls.
My notes used to be just "problem -> solution." Now I keep a tiny list of failed attempts too, including how long I tested each one. Otherwise six months later I confidently reinstall the same driver again.
For people who keep repair or debugging notes: what do you actually bother recording? Full logs become a junk drawer for me, but the one-line version keeps leaving out the important bit.