Which advice about tools did you eventually ignore after a few failed attempts?

Noah Miller · 15 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.

Isha Menon · 14 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 am curious whether java still feels good next month.

Hugo Sánchez · 9 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 · 4 likes

Same here. It took me too long to learn.

Rafael Almeida · 0 likes

I had the same reaction to better.

Noah Miller · 8 likes

I am cheering for this update. I noticed the same thing in São Paulo.

Tiny Baker · 4 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 pairs weirdly well with lentil soup.

Kabir Khan · 3 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.

Curious Atlas · 9 likes

Exactly; the hidden cost is energy.

Sebastián Rojas · 3 likes

Totally agree, especially for beginners.

Valeria López · 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 Madrid example makes it feel concrete.

Mateo Cruz · 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. It reminds me of a very specific conversation near the train station.

Grace Parker · 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. It reminds me of a very specific conversation near a tiny balcony.

Piotr Zieliński · 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. The Manila example makes it feel concrete.

Arif Hasan · 1 likes

This is the kind of useful internet I still show up for. I care less about the perfect answer and more about repeatability.