What would you do first if you were new to Programming without overthinking it?

Gentle Comet · 10 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I care less about the perfect answer and more about repeatability

Giulia Rossi · 4 likes

I do not have a strong take, but teh were detail is useful. I would write it down before changing anything else

Tola Ibrahim · 8 likes

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

Olena Shevchenko · 7 likes

helpful correction

Sleepy Comet · 4 likes

I needed the reminder to start smaller

Silver Lantern · 4 likes

Try making a tiny reproduction with no framework code. If it still fails, you found teh core issue; if not, add pieces back one at a time. I would test it for 9 days before deciding

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

Noah Miller · 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. A little friction removed goes a long way

Emma Tremblay · 0 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The low-effort version is probably the keeper