Programming · by Paolo Garcia · 2026-09-29
What is worth spending money on for debugging on a budget?
Part of me wanted the fancy version with all the tools. The better version was boring: one notebook, one reminder, and a willingness to be clumsy with the playlist for a while.
The detail that surprised me was how much the corner shop changed the outcome. Same plan, different setting, completely different energy.
31 sparks · 10 comments
Comments
Sleepy Baker · 6 likes
Start by reducing it to the smallest reproducible piece, then change one variable at a time. If two options look equal, choose the one that is easier to reverse.
- 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.
Cozy Coder · 6 likes
Start by reducing it to the smallest reproducible piece, then change one variable at a time. If two options look equal, choose the one that is easier to reverse.
- 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.
Come back with what happened; the details will make the next answer better.
Tola Ibrahim · 1 likes
Totally agree, especially for beginners.
Sophie Gagnon · 1 likes
Start by reducing it to the smallest reproducible piece, then change one variable at a time. The trap is trying to optimize before you have feedback.
- 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 · 1 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The 8-minute rule is underrated.