What mistake taught you the most about performance after a few failed attempts?

Solar Baker · 8 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 is where I would ask one more question before choosing

Hugo Martin · 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. I care less about the perfect answer and more about repeatability

Arif Hasan · 12 likes

I am curious what changed your mind

Maya Williams · 4 likes

I was going to disagree, but your second sentence got me

Chloe Davis · 6 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I noticed the same thing in Dublin

João Pereira · 1 likes

Now I want a spreadsheet

Noah Miller · 3 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. My only addition is to make the first step visible

Midnight Sparrow · 4 likes

That is the part people skip

Jiho Lee · 2 likes

That sounds great until you add children/pets/deadlines

Aria Thompson · 3 likes

Can you expand on that a bit?

Rapid Panda · 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 9 weeks