What is worth spending money on for javascript as a beginner?

João Pereira · 20 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 where I would ask one more question before choosing

Liam Eriksson · 19 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 constraint is probably the real story

Curious Fern · 15 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The low-effort version is probably the keeper

Siti Lestari · 11 likes

Good reminder that boring can be good. I care less about the perfect answer and more about repeatability

Hugo Sánchez · 8 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 keep a note about performance for exactly this reason

Huy Le · 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. My friend tried it in Buenos Aires and had the opposite result

Piotr Zieliński · 3 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

Midnight Otter · 11 likes

noted, and thank you

Haruto Sato · 8 likes

good clarification — I read it differently at first

Budi Santoso · 1 likes

Can you expand on that a bit?

Isha Menon · 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. This is more useful on a tired late summer then on a perfect day

Diego García · 3 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

Gentle Baker · 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. A little friction removed goes a long way

Camille Dubois · 1 likes

I wish more posts had this much context. This is where I would ask one more question before choosing. I would love to see the benchmark numbers

Tiny Atlas · 11 likes

could be regional too

Rafael Almeida · 10 likes

I laughed, but you are not wrong

Tola Ibrahim · 3 likes

That is the part people skip

Maya Putri · 4 likes

noted, and thank you

Kabir Khan · 1 likes

Appreciate the nuance

Jonas Schneider · 3 likes

That is a good boundary

Alma Nilsson · 1 likes

What would you change if you started over? The Toronto example makes it feel concrete

Tiny Runner · 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. I learned that one the expensive way

Sofía Hernández · 1 likes

You explained the tradeoff really clearly. I would write it down before changing anything else. This is exactly the kind of tradeoff teams argue about for weeks

Amina Okafor · 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. The quiet Sunday version is even more interesting

Sara Ahmed · 3 likes

@amina-58 Fair pushback