Web Dev · by Avery Johnson · 2026-09-25

How would you solve this first week problem with javascript with limited time?

I had a disappointing first try, a surprisingly good second try, and then a third attempt that taught me humility. So, naturally, I now have opinions.

My current rule is simple: if it takes less than 6 minutes to prepare, I am much more likely to keep doing it.

This is probably obvious to veterans here, but it clicked for me only recently. backend got easier when I stopped treating every attempt like a final exam.

4 sparks · 3 comments

Comments

Mariam Al Mansoori · 1 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.

That should give you a solid first pass.

Urban Rider · 0 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 where I would ask one more question before choosing.

Miguel Santos · 1 likes

I needed the reminder to start smaller.