Programming · by Emma Tremblay · 2026-09-13
How would you solve this busy month problem with debugging without fancy tools?
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.
Would love to hear how other people handle this. I am especially curious about the version that works on a tired weekday, not just on an ideal Sunday
87 sparks · 21 comments
Comments
Laura Gómez · 10 likes
Try making a tiny reproduction with no framework code. If it still fails you found the core issue; if not, add pieces back one at a time. For me it came down to the first draft
Rohan Mehta · 7 likes
Try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. I learned that one the expensive way
Emma Tremblay · 6 likes
Try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. The surprising part is easy to underestimate
Brave Sparrow · 6 likes
there is a hidden assumption here that not everyone shares. Honestly, the simplest version wins for me
Bianca Santos · 6 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I keep a note about learning for exactly this reason
Iryna Melnyk · 3 likes
The vibe here is immaculate. I would write it down before changing anything else
Solar Noodle · 16 likes
short answer: yes. Long answer: also yes
Avery Johnson · 1 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. That is the kind of detail beginners miss
Amelia Hughes · 0 likes
that is fair, but I still worry about maintenance
Ren Suzuki · 1 likes
the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I would love to see a follow-up after 6 weeks
Rizky Pratama · 0 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. I care less about the perfect answer and more about repeatability
Rizky Pratama · 0 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The messy constraint is probably the real story
Grace Parker · 0 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. That is where the boring checklist helps