Programming · by Noah Miller · 2026-10-05

What would you do first if you were new to Programming in real life?

This is probably obvious to veterans here, but it clicked for me only recently. debugging got easier when I stopped treating every attempt like a final exam.

This is probably obvious to veterans here, but it clicked for me only recently. debugging got easier when I stopped treating every attempt like a final exam

39 sparks · 16 comments

Comments

[deleted] · 7 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. This is more useful on a tired late summer then on a perfect day

Mango Mango · 5 likes

Start by reducing it to the smallest reproducible piece, then change one variable at a time. You will learn more from a simple version repeated three times than from a perfect plan you never start.

- 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.

That should give you a solid first pass

Haruto Sato · 3 likes

Now I want a spreadsheet

Siti Lestari · 0 likes

anecdote beats theory here

João Pereira · 2 likes

Thanks that actually helped

Mango Mango · 1 likes

Can you expand on that a bit?

Omar Hassan · 1 likes

Totally agree, especially for beginners

Nour Ali · 0 likes

Exactly; the hidden cost is energy

Grace Parker · 1 likes

I think both things can be true

Noah Miller · 1 likes

I am stealing that phrase

Luca Bianchi · 0 likes

could be regional too

Noah Miller · 1 likes

Thanks that actually helped

Noah Miller · 1 likes

kind of wild how often regional is the whole issue

Ngozi Bello · 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.

That should give you a solid first pass

Valeria López · 1 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

Jack Taylor · 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. This is more useful on a tired commute then on a perfect day