Which advice about architecture did you eventually ignore on a budget?

Grace Parker · 8 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 would have saved me a lot of trial and error.

Urban Comet · 3 likes

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

Sleepy Lantern · 5 likes

That is a much better way to say it.

Diego García · 1 likes

That is a much better way to say it.

Midnight Runner · 1 likes

Exactly; the hidden cost is energy.

Maya Putri · 1 likes

I am curious what changed your mind.

Rapid Marauder · 0 likes

That is a much better way to say it.

Urban Comet · 2 likes

The Tuesday test is undefeated.

Lina Keller · 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 am curious whether debugging still feels good next month.

Gentle Comet · 26 likes

@lina-84 My wallet felt that.

Maya Putri · 2 likes

I had the same reaction to those.

Lina Keller · 0 likes

@quiet_maya26 Small caveat: context changes the answer a lot.

Tiny Atlas · 1 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.

Diego García · 1 likes

I think the bad version of this advice causes a lot of frustration. I noticed the same thing in Buenos Aires.

Isha Menon · 0 likes

I needed the reminder to start smaller.

Huy Le · 1 likes

Excellent timing; I was just thinking about budget. For me it came down to the tiny repair. Naming things remains undefeated as the hardest problem.

Tola Ibrahim · 10 likes

I like this more than the top-level advice.

Finn Brown · 0 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 rainy evening than on a perfect day.

Liam Eriksson · 0 likes

That last line is excellent. The messy part is easy to underestimate.

João Pereira · 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. This is more useful on a tired quiet Sunday than on a perfect day.

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

Nicolás Díaz · 0 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. That is where the boring checklist helps.