Web Dev · by Kabir Khan · 2026-09-04
What would you do first if you were new to Web Dev without overthinking it?
33 sparks · 9 comments
Web Dev · by Kabir Khan · 2026-09-04
33 sparks · 9 comments
Mariana Costa · 21 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.
Kabir Khan · 9 likes
This is the kind of disagreement I like.
Noah Miller · 1 likes
Beautifully concise.
Ethan Brooks · 1 likes
Good clarification — I read it differently at first.
Daniel Kiptoo · 11 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!
Tola Ibrahim · 2 likes
Amazing how much difference one small change can make. The a neighborhood park detail changes the whole answer.
Anna Gruber · 2 likes
I would love a follow-up example.
Mango Rider · 0 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.
Aoi Ito · 0 likes
Helpful and not preachy, which is rare. My only addition is to make the first step visible.