Programming · by Hugo Sánchez · 2026-09-17
How do you stay consistent when debugging gets boring on a budget?
Context: I am not an expert, just someone trying to make Programming feel less intimidating. I wrote down what worked, what felt awkward, and what I would do differently next time.
My current rule is simple: if it takes less than 7 minutes to prepare, I am much more likely to keep doing it.
50 sparks · 6 comments
Comments
Emma Tremblay · 3 likes
I would log the input, the expected output and the actual output first. Once those three are visible, the bug usually stops feeling mysterious. The 9-minute rule is underrated.
Hugo Sánchez · 2 likes
This is the kind of disagreement I like.
Hugo Sánchez · 1 likes
@emma-53 Small caveat: context changes the answer a lot.
Lotte Jansen · 1 likes
Start by reducing it to the smallest reproducible piece, then change one variable at a time. Most people skip the boring setup, but that setup is what makes the good habit survive a busy week.
- Write down the exact error and the input that caused it.
- Make a tiny example, then add pieces back slowly.
- Keep the final fix boring and well-named.
Source: mostly hard-won experience and comparing notes with people who stuck with it.
Sara Ahmed · 4 likes
I was going to disagree, but your second sentence got me.