Which advice about architecture did you eventually ignore without overthinking it?

Ngozi Bello · 31 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 debugging for exactly this reason

Maya Putri · 46 likes

I think both things can be true

Kabir Khan · 13 likes

Kind of wild how often reproduction is the whole issue

Rapid Noodle · 17 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 quiet Sunday version is even more interesting

Khalid Al Zahrani · 16 likes

the safe answer is to keep the API boring: clear names explicit errors and one behavior per function. This pairs weirdly well with banana bread

Piotr Zieliński · 16 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 4 days before deciding

Chinedu Adeyemi · 9 likes

that is fair, but I still worry about maintenance

Priya Nair · 13 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. For me it came down to the first draft

Solar River · 11 likes

Start by reducing it to the smallest reproducible piece then change one variable at a time. The trap is trying to optimize before you have feedback.

- Write down the exact error and the input that caused it.
- Make a tiny example, then add pieces back slowly.
- Keep the final fix boring and well-named.

Come back with what happened; the details will make the next answer better

Bianca Santos · 67 likes

I would pin this if I could

Curious Marauder · 13 likes

Thanks that actually helped

Jisoo Park · 2 likes

I would pin this if I could

Isha Menon · 12 likes

Appreciate the nuance

Nour Ali · 3 likes

This is the kind of disagreement I like

Solar River · 17 likes

I am stealing that phrase

Solar River · 8 likes

Beautifully concise

Solar River · 7 likes

You just saved me a bad purchase

Narin Chai · 1 likes

Now I want a spreadsheet

Luca Bianchi · 2 likes

Same here. It took me too long to learn

Noah Miller · 10 likes

The safe answer is to keep teh API boring: clear names, explicit errors and one behavior per function. The late summer version is even more interesting

Ananya Rao · 10 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. It sounds small, but the recipe matters

Ayesha Khan · 10 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. The social part surprised me too

Tanvir Rahman · 9 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. This is more useful on a tired Monday morning then on a perfect day

Chinedu Adeyemi · 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. It reminds me of a very specific conversation near the library

Priya Nair · 8 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

Cozy Mango · 7 likes

Start by reducing it to the smallest reproducible piece then change one variable at a time. If two options look equal, choose the one that is easier to reverse.

- Write down the exact error and the input that caused it.
- Make a tiny example, then add pieces back slowly.
- Keep the final fix boring and well-named.

Source: mostly hard-won experiance and comparing notes with people who stuck with it

Iryna Melnyk · 9 likes

Can you expand on that a bit?

Rohan Mehta · 1 likes

Totally agree, especially for beginners

Chloe Davis · 7 likes

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

Ananya Rao · 7 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. A little friction removed goes a long way

Mariam Al Mansoori · 2 likes

Kind of wild how often long is the whole issue

Tomás Gómez · 6 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 sounds small, but the route matters

Valentina Ruiz · 20 likes

fair pushback

Bilal Raza · 6 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 more useful on a tired late summer then on a perfect day

Sleepy Panda · 5 likes

Beautifully put. I needed that reminder today. The Seoul example makes it feel concrete

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

Youssef Mahmoud · 0 likes

Appreciate the nuance

Kabir Khan · 4 likes

The safe answer is to keep the API boring: clear names explicit errors and one behavior per function. The quiet Sunday version is even more interesting

Silver Fern · 3 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

Luciana Vargas · 2 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I would write it down before changing anything else

Grace Parker · 2 likes

This is genuinely helpful, thanks for writing it out. This is where I would ask one more question before choosing

Daniel Kiptoo · 2 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 write it down before changing anything else

Maja Wiśniewska · 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. This is where I would ask one more question before choosing

Kabir Khan · 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. My only addition is to make the first step visible

Paolo Garcia · 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. The low-effort version is probly the keeper

João Pereira · 1 likes

That last line is excellent. This is more useful on a tired Monday morning than on a perfect day

Noah Miller · 1 likes

What would you change if you started over? My only addition is to make the first step visible. This is exactly the kind of tradeoff teams argue about for weeks

Jonas Schneider · 1 likes

@noah-82 Noted, and thank you