Web Dev · by Ethan Brooks · 2026-09-09
What is worth spending money on for performance as a beginner?
Part of me wanted the fancy version with all the tools. The better version was boring: one notebook, one reminder, and a willingness to be clumsy with the first draft for a while.
This is probably obvious to veterans here, but it clicked for me only recently. css got easier when I stopped treating every attempt like a final exam.
53 sparks · 22 comments
Comments
Khalid Al Zahrani · 31 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.
Noah Campbell · 2 likes
Small caveat: context changes the answer a lot.
Ethan Brooks · 20 likes
@midnight_noah40 I am curious what changed your mind.
Tiago Costa · 3 likes
I think this advice is overrated. I would test it for 9 days before deciding.
Aarav Sharma · 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 used to overcomplicate this constantly.
Omar Hassan · 2 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I would write it down before changing anything else.
Aoi Ito · 2 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. That is where the boring checklist helps.
Noah Meier · 1 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 · 1 likes
Helpful and not preachy, which is rare. This pairs weirdly well with tacos.
Sleepy Runner · 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.
Theo Bennett · 1 likes
Good clarification — I read it differently at first.
Maja Wiśniewska · 1 likes
Agree completely. The simple version is underrated. I learned that one the expensive way.
Ren Suzuki · 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 low-effort version is probably the keeper.
Felix Weber · 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. I keep a note about javascript for exactly this reason.
Urban Baker · 0 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. It reminds me of a very specific conversation near a tiny balcony.
Rizky Pratama · 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. The social part surprised me too.
Hugo Martin · 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. My friend tried it in Istanbul and had the opposite result.