What are the red flags beginners miss in Web Dev?

Sanne de Vries · 9 likes

Start by reducing it to the smallest reproducible piece, then change one variable at a time. Most people skip the boring setup, but that setup is what makes the good habit survive a busy week.

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

Mariana Costa · 4 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.

Hope this helps!

Noor Janssens · 16 likes

I would love a follow-up example.

Budi Santoso · 0 likes

@paper_noodle18 Kind of wild how often repeated is the whole issue.

Benjamín Rojas · 4 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I care less about the perfect answer and more about repeatability.

Rizky Pratama · 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 Cape Town example makes it feel concrete.

Piotr Zieliński · 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. I learned that one the expensive way.

Solar Fern · 2 likes

I needed the reminder to start smaller.

Kabir Khan · 0 likes

@marauderPilot89 That is the part people skip.

Anna Gruber · 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 first week than on a perfect day.

Paolo Garcia · 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. The social part surprised me too.