Web Dev · by Urban Baker · 2026-09-21
What mistake taught you the most about performance without overthinking it?
> Tiny progress is still progress.
That line sounds cheesy, but it got me through the part where performance stopped feeling new.
I tried this in Lagos with a friend and we both noticed the same thing: the social part mattered more than the perfect plan.
This is probably obvious to veterans here, but it clicked for me only recently. ux got easier when I stopped treating every attempt like a final exam.
10 sparks · 4 comments
Comments
Miguel Santos · 12 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.
Source: mostly hard-won experience and comparing notes with people who stuck with it.
Camila Soto · 6 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.
Come back with what happened; the details will make the next answer better.
Aarav Sharma · 2 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. This pairs weirdly well with idli.
Pixel Otter · 1 likes
Start by reducing it to the smallest reproducible piece, then change one variable at a time. The trap is trying to optimize before you have feedback.
- 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.