What mistake taught you the most about debugging when life is busy?

Ananya Rao · 17 likes

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

Priya Nair · 3 likes

That is a much better way to say it.

Piotr Zieliński · 2 likes

Thanks, that actually helped.

Mariam Said · 2 likes

This. Exactly this.

Jasmine Cruz · 1 likes

I am stealing that phrase.

Silver Coder · 1 likes

Thanks for making it less intimidating.

Ananya Rao · 1 likes

I think both things can be true.

Budi Santoso · 8 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 experience and comparing notes with people who stuck with it.

Cedar Otter · 1 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.