Orbit · Explore

Web Dev · by Huy Le · 2026-09-08

What is the kindest way to start with performance without fancy tools?

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 recipe for a while.

14 sparks · 4 comments

Comments

Tiny Comet · 9 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.

Come back with what happened; the details will make the next answer better.

Ethan Brooks · 7 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 would test it for 6 days before deciding.

Maja Wiśniewska · 1 likes

Small caveat: context changes the answer a lot.

Pixel Noodle · 2 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!