How would you solve this lunch break problem with javascript with limited time?

Brave Atlas · 6 likes

There is a hidden assumption here that not everyone shares. That is where the boring checklist helps

Aoi Ito · 5 likes

good reminder that boring can be good. I care less about the perfect answer and more about repeatability. The boring solution is probably the reliable one here

Theo Bennett · 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 noticed the same thing in Berlin

Mango Otter · 4 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

Mariam Said · 3 likes

Love the tiny experiment energy. The 5-minute rule is underrated

Solar Fern · 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. I learned that one the expensive way

Haruto Sato · 2 likes

I wish more posts had this much context. The the corner shop detail changes the whole answer. A small test case would make this easier to trust

Mateo Cruz · 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 keep a note about backend for exactly this reason

Maya Putri · 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 test it for 6 days before deciding

Nicolás Díaz · 11 likes

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

An Pham · 2 likes

Same here. It took me too long to learn

Paolo Garcia · 1 likes

That made the concept click

Paper Marauder · 0 likes

I think both things can be true

Ren Suzuki · 5 likes

The Tuesday test is undefeated

Achieng Njeri · 1 likes

could be regional too

Sleepy Baker · 8 likes

That sounds great until you add children/pets/deadlines

Rizky Pratama · 7 likes

Now I want a spreadsheet

Haruto Sato · 0 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

Luca Bianchi · 0 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. It reminds me of a very specific conversation near the corner shop