How would you solve this first week problem with debugging on a budget?

Aoi Ito · 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. That is the kind of detail beginners miss

Mariam Said · 2 likes

You just saved me a bad purchase

Sara Hosseini · 10 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. That is where the boring checklist helps

Mango Orbit · 9 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 São Paulo

Nour Ali · 2 likes

This is the gentle version of my rant

Gentle Runner · 9 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

Sleepy Otter · 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 keep a note about learning for exactly this reason

Youssef Mahmoud · 4 likes

The safe answer is to keep the API boring: clear names explicit errors and one behavior per function. I learned that one the expensive way

Cian Kelly · 11 likes

The Tuesday test is undefeated

Beatriz Sousa · 13 likes

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

Ethan Brooks · 4 likes

the safe answer is to keep the API boring: clear names explicit errors and one behavior per function. My friend tried it in Buenos Aires and had the opposite result

Camille Dubois · 4 likes

Great point, especially the part about debugging

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

Oliver Smith · 0 likes

Exactly; the hidden cost is energy

Emir Kaya · 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. It reminds me of a very specific conversation near the train station

Rafael Almeida · 2 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. The late summer version is even more interesting

Sara Ahmed · 5 likes

I think both things can be true

Danylo Kovalenko · 3 likes

short answer: yes. Long answer: also yes

João Pereira · 0 likes

You just saved me a bad purchase

Mara Fischer · 2 likes

Amazing how much difference one small change can make. The lunch break version is even more interesting

Maya Williams · 3 likes

Appreciate the nuance

Oussama Alaoui · 1 likes

Glad you shared it; small wins count. For me it came down to the route

Diego García · 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. I keep a note about debugging for exactly this reason

Maya Williams · 2 likes

I think both things can be true

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

Mariam Said · 0 likes

Excellent timing; I was just thinking about budget. The 6-minute rule is underrated