Web Dev · by Rohan Mehta · 2026-09-21
Why does performance feel easy for everyone except me in real life?
> Tiny progress is still progress.
That line sounds cheesy, but it got me through the part where ux stopped feeling new.
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.
I know this is a tiny sample size, but after 8 attempts the pattern is pretty clear. When I keep the setup simple, I actually follow through.
53 sparks · 18 comments
Comments
Noé Petit · 13 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.
Source: mostly hard-won experience and comparing notes with people who stuck with it.
Siti Lim · 10 likes
I am cheering for this update. For me it came down to the practice run.
Tiago Costa · 5 likes
Love the tiny experiment energy. I would test it for 5 days before deciding.
Aoi Ito · 3 likes
The best answer in the thread, honestly.
Hugo Martin · 3 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 noticed the same thing in Nairobi.
Maksym Bondar · 2 likes
The vibe here is immaculate. This pairs weirdly well with ramen.
Rohan Mehta · 1 likes
This comment has main-character footnote energy.
Siti Lestari · 1 likes
Not wrong, but I think this underestimates how different people's constraints are. For me it came down to the conversation.
Olena Shevchenko · 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 would love to see a follow-up after 5 weeks.
Cedar Comet · 0 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The the train station detail changes the whole answer.
Paolo Garcia · 0 likes
I think the bad version of this advice causes a lot of frustration. For me it came down to the setup.
Yui Tanaka · 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. It reminds me of a very specific conversation near my desk.
Emma Tremblay · 0 likes
That sounds great until you add children/pets/deadlines.