What is the kindest way to start with performance?

Jisoo Park · 17 likes

Really good advice, and it feels doable. That is where the boring checklist helps

Valeria López · 14 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

Midnight Atlas · 13 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. This pairs weirdly well with pasta

Youssef Mahmoud · 11 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 Berlin

Luciana Vargas · 8 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 would have saved me a lot of trial and error

Midnight Marauder · 6 likes

there is a hidden assumption here that not everyone shares. I used to overcomplicate this constantly

Rizky Pratama · 10 likes

Small caveat: context changes the answer a lot

Aoi Ito · 6 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. This would have saved me a lot of trial and error

Nusrat Akter · 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. This is where I would ask one more question before choosing

Urban Orbit · 4 likes

This feels a little overrated to me, even if the intention is good. This pairs weirdly well with arepas

Camille Dubois · 3 likes

that is a surprisingly elegant way to frame it. That is the kind of detail beginners miss

Thandi Mokoena · 3 likes

I am curious what changed your mind

Arif Hasan · 3 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. My only addition is to make the first step visible

Jisoo Park · 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. The my desk detail changes the whole answer

Maya Williams · 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. My friend tried it in Lagos and had the opposite result

Ngozi Bello · 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. The surprising constraint is probably the real story

Rizky Pratama · 1 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I would love to see a follow-up after 3 weeks

Urban Runner · 7 likes

helpful correction

Cedar Atlas · 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 would love to see a follow-up after 7 weeks