What is the kindest way to start with performance in real life?

Léa Bernard · 7 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. It reminds me of a very specific conversation near the train station

Maya Putri · 0 likes

Exactly; the hidden cost is energy

Urban Orbit · 6 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. That is the kind of detail beginners miss

Mango Panda · 6 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 care less about the perfect answer and more about repeatability

Huy Le · 5 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 banana bread

Ngozi Bello · 5 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 am curious whether javascript still feels good next month

Quiet Runner · 5 likes

I would log teh input, teh expected output and teh actual output first. Once those three are visible, teh bug usually stops feeling mysterious. This would have saved me a lot of trial and error

Sleepy Marauder · 1 likes

Now I want a spreadsheet

Aria Thompson · 3 likes

I would log teh input, teh expected output and teh actual output first. Once those three are visible, teh bug usually stops feeling mysterious. This would have saved me a lot of trial and error

Olena Shevchenko · 1 likes

Helpful and not preachy, wich is rare. That is the kind of detail beginners miss

Haruto Sato · 5 likes

Can you expand on that a bit?

Priya Nair · 1 likes

This comment has main-character footnote energy

Noah Miller · 2 likes

I like this more then the top-level advice

Noé Petit · 0 likes

Thanks for making it less intimidating

Diego Quispe · 7 likes

That is the part people skip

Zeynep Demir · 0 likes

I needed the reminder to start smaller

Ethan Brooks · 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 the corner shop detail changes the whole answer

Mia Anderson · 4 likes

I would pin this if I could

Martina Fernández · 0 likes

helpful correction

Ayesha Khan · 1 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The Kuala Lumpur example makes it feel concrete

Isha Menon · 1 likes

The vibe here is immaculate. The Seoul example makes it feel concrete

Cozy Rider · 1 likes

I would log teh input, teh expected output and teh actual output first. Once those three are visible, teh bug usually stops feeling mysterious. I would write it down before changing anything else

Priya Nair · 5 likes

Appreciate the nuance

Siti Lestari · 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. I am curious whether css still feels good next month

Gentle Marauder · 0 likes

the safe answer is to keep the API boring: clear names explicit errors and one behavior per function. The first week version is even more interesting