What would you do first if you were new to Web Dev without fancy tools?

Quiet Orbit · 41 likes

I think this advice is overrated. This is more useful on a tired first week than on a perfect day.

Gentle Mango · 1 likes

Fair pushback.

Felix Weber · 12 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The Nairobi example makes it feel concrete.

Omar Hassan · 4 likes

This comment has main-character footnote energy.

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

Nusrat Akter · 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 am curious whether javascript still feels good next month.

Thandi Mokoena · 7 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.

Beatriz Sousa · 4 likes

Yep, the boring details matter.

Rohan Mehta · 30 likes

I like this more than the top-level advice.

Yui Tanaka · 4 likes

That is a much better way to say it.

Beatriz Sousa · 7 likes

Short answer: yes. Long answer: also yes.

Marco Conti · 2 likes

That is a much better way to say it.

Haruto Sato · 7 likes

What happened after the first week? I am curious whether without stayed easy. I care less about the perfect answer and more about repeatability.

Budi Santoso · 6 likes

Love the tiny experiment energy. A little friction removed goes a long way.

Solar Lantern · 6 likes

What would you change if you started over? This pairs weirdly well with idli.

Bianca Santos · 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. Honestly, the simplest version wins for me.

Chloe Davis · 3 likes

Now I want a spreadsheet.

Sebastián Rojas · 4 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.

Hope this helps!

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

Brave Atlas · 3 likes

Good reminder that boring can be good. The boring solution is probably the reliable one here.

Rohan Mehta · 3 likes

There is a hidden assumption here that not everyone shares. I care less about the perfect answer and more about repeatability.

Paolo Garcia · 7 likes

I had the same reaction to hidden.

Miguel Santos · 7 likes

Noted, and thank you.

Gentle Baker · 3 likes

Big fan of this approach.

Pixel Orbit · 2 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.

Noah Miller · 3 likes

I laughed, but you are not wrong.

Kabir Khan · 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 busy month version is even more interesting.

Ethan Brooks · 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. I would write it down before changing anything else.

Luciana Vargas · 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 Mexico City example makes it feel concrete.