How do you know when to stop tweaking performance after a few failed attempts?

Mariam Said · 9 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 4 weeks

Linh Tran · 2 likes

the context helps. Without it I would of assumed the opposite. I care less about the perfect answer and more about repeatability

Silver Noodle · 1 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

Mateo Cruz · 8 likes

I think both things can be true

Camila Rocha · 7 likes

The Tuesday test is undefeated

Valeria López · 3 likes

I am curious what changed your mind

Midnight Mango · 0 likes

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