Which advice about architecture did you eventually ignore after a few failed attempts?

Ren Suzuki · 53 likes

start by reducing it to the smallest reproducible piece, then change one variable at a time. Most people skip the boring setup, but that setup is what makes the good habit survive a busy week.

- 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

Jasmine Cruz · 10 likes

The Tuesday test is undefeated

Chinedu Adeyemi · 2 likes

adding this to my notes

Mango Mango · 43 likes

start by reducing it to the smallest reproducible piece, then change one variable at a time. You will learn more from a simple version repeated three times than from a perfect plan you never start.

- 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

Chinedu Adeyemi · 5 likes

Beautifully concise

Mango Mango · 7 likes

that is fair, but I still worry about maintenance

Mango Mango · 3 likes

@chinedu-55 The best answer in the thread, honestly

Midnight Baker · 2 likes

Totally agree, especially for beginners

Mango Mango · 1 likes

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

Mariam Said · 2 likes

Thanks that actually helped

Mango Mango · 1 likes

That is the part people skip

Chinedu Adeyemi · 4 likes

Appreciate the nuance

Noah Miller · 3 likes

I am stealing that phrase

Ren Suzuki · 3 likes

good clarification — I read it differently at first

Rafael Almeida · 52 likes

I am stealing that phrase

Miguel Santos · 1 likes

I laughed, but you are not wrong

Aarav Sharma · 1 likes

This. Exactly this

Rohan Mehta · 1 likes

This is the kind of disagreement I like

Mango Mango · 1 likes

This is the kind of disagreement I like

Khalid Al Zahrani · 1 likes

good clarification — I read it differently at first

Aoi Ito · 0 likes

Thanks that actually helped

Noah Miller · 1 likes

could be regional too

Aarav Sharma · 1 likes

that is fair, but I still worry about maintenance

Ren Suzuki · 29 likes

Start by reducing it to the smallest reproducible piece, then change one variable at a time. Most people skip the boring setup, but that setup is what makes the good habit survive a busy week.

- 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.

That should give you a solid first pass

Chiara Romano · 16 likes

Love the tiny experiment energy. My only addition is to make the first step visible

Camila Rocha · 3 likes

I think both things can be true

Ethan Brooks · 16 likes

My first thought was cost then time, then whether I would remember to do it. The low-effort version is probly the keeper

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

Valeria López · 6 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. The Melbourne example makes it feel concrete

Curious Orbit · 6 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

Yasmine El Amrani · 4 likes

Interesting. I would like to see how it changes after 2 months. The awkward constraint is probably the real story. Naming things remains undefeated as the hardest problem

Rafael Almeida · 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. This would have saved me a lot of trial and error

Sara Hosseini · 1 likes

Can you expand on that a bit?

Maya Putri · 3 likes

This is genuinely helpful, thanks for writing it out. My friend tried it in Istanbul and had the opposite result

Nicolás Díaz · 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. The 7-minute rule is underrated

Jonas Schneider · 2 likes

this sounds sensible, though I would need to test it myself. The late summer version is even more interesting

Amelia Hughes · 2 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. That is the kind of detail beginners miss

Urban Marauder · 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. For me it came down to the routine

Cedar Runner · 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 winter version is even more interesting

Elsa Andersson · 1 likes

I appreciate the honest middle stage, not just the polished ending. The boring solution is probably the reliable one here

Amina Okafor · 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. For me it came down to the first draft

Emir Kaya · 0 likes

Do you think this would work in a smaller place than Jakarta?