What would you do first if you were new to Programming when life is busy?

Chinedu Adeyemi · 20 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.

Come back with what happened; the details will make the next answer better

Camille Dubois · 7 likes

that is fair, but I still worry about maintenance

João Pereira · 21 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. That is the kind of detail beginners miss

Tola Ibrahim · 21 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 4-minute rule is underrated

Élodie Favre · 16 likes

Love the tiny experiment energy. The Seoul example makes it feel concrete

Tola Ibrahim · 217 likes

You just saved me a bad purchase

Mateo Cruz · 31 likes

Exactly; the hidden cost is energy

Jack Taylor · 6 likes

I am curious what changed your mind

Sleepy Sparrow · 4 likes

kind of wild how often feel is the whole issue

Mariam Said · 8 likes

I laughed, but you are not wrong

Maya Williams · 4 likes

I am stealing that phrase

Jonas Schneider · 3 likes

Thanks that actually helped

Maya Putri · 2 likes

my wallet felt that

Grace Parker · 1 likes

I was going to disagree, but your second sentence got me

Urban Baker · 14 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 commute version is even more interesting

Elif Yılmaz · 11 likes

This is genuinely helpful thanks for writing it out. I keep a note about debugging for exactly this reason

Paolo Garcia · 1 likes

helpful correction

Maja Wiśniewska · 8 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. This is where I would ask one more question before choosing

Solar Fern · 8 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. It sounds small, but the first draft matters

Solar Marauder · 9 likes

fair pushback

Liam Eriksson · 9 likes

that is fair, but I still worry about maintenance

Bianca Santos · 4 likes

good clarification — I read it differently at first

Bianca Santos · 1 likes

@solar-46 Helpful correction

Mateo Cruz · 1 likes

The best answer in the thread, honestly

Piotr Zieliński · 1 likes

That is the part people skip

Liam Wilson · 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. This is more useful on a tired rainy evening than on a perfect day

Camila Rocha · 5 likes

adding this to my notes

Chiara Romano · 7 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I am curious whether learning still feels good next month

Felix Weber · 6 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 first week version is even more interesting

Iryna Melnyk · 5 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 would love to see a follow-up after 8 weeks

Felix Weber · 6 likes

short answer: yes. Long answer: also yes

Tomás Gómez · 4 likes

this depends heavily on budget, time and personality. I would love to see the benchmark numbers

Theo Bennett · 10 likes

That is a good boundary

Nour Ali · 3 likes

This is the kind of useful internet I still show up for. This pairs weirdly well with bibimbap

Mariam Said · 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 a neighborhood park detail changes the whole answer

Luciana Vargas · 2 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. A little friction removed goes a long way

Lina Al Harbi · 2 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 lunch break version is even more interesting

Kabir Khan · 2 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 rainy evening version is even more interesting

Ananya Rao · 7 likes

Beautifully concise

Hugo Sánchez · 2 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 2-minute rule is underrated

Diego García · 1 likes

The kindness in this post is lovely. The awkward constraint is probably the real story

Ananya Rao · 1 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. This is where I would ask one more question before choosing

Lucas Dubois · 0 likes

This is genuinely helpful, thanks for writing it out. The 8-minute rule is underrated

Mateo Cruz · 0 likes

Try making a tiny reproduction with no framework code. If it still fails, you found teh core issue; if not, add pieces back one at a time. I would test it for 9 days before deciding