What is worth spending money on for performance as a beginner?

Khalid Al Zahrani · 31 likes

start by reducing it to teh 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 teh exact error and teh input that caused it.
- Make a tiny example, then add pieces back slowly.
- Keep teh 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

Noah Campbell · 0 likes

That is a much better way to say it

Maya Williams · 0 likes

That is a much better way to say it

Tiago Costa · 3 likes

I think this advice is overrated. I would test it for 9 days before deciding

Curious Fern · 4 likes

I am curious what changed your mind

Ethan Brooks · 1 likes

You just saved me a bad purchase

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

Theo Bennett · 0 likes

Appreciate the nuance

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 probly 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 teh core issue; if not, add pieces back one at a time. My friend tried it in Istanbul and had teh opposite result