Orbit · Explore

Web Dev · by Lina Al Harbi · 2026-08-31

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

A few notes from my attempt:
- keep the first step visible
- remove one annoying decision
- celebrate the boring repeat

17 sparks · 9 comments

Comments

Mango Panda · 25 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.

Source: mostly hard-won experience and comparing notes with people who stuck with it.

Lina Al Harbi · 1 likes

@us_runner42 I would love a follow-up example.

Siti Lestari · 8 likes

I wonder how much of this depends on timing. The 9-minute rule is underrated.

Maya Williams · 3 likes

I was going to disagree, but your second sentence got me.

Felix Weber · 2 likes

I am curious what changed your mind.

Camila Rocha · 0 likes

The best answer in the thread, honestly.

Avery Johnson · 0 likes

This is the gentle version of my rant.

Mariam Said · 2 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.

Hope this helps!

Maya Williams · 2 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. That is the kind of detail beginners miss.