Orbit · Explore

Programming · by Luca Bianchi · 2026-09-02

What is worth spending money on for debugging?

I started this because my rainy evening felt a little stuck, and tools seemed like a manageable place to experiment. The funny part is that the smallest change was the one I kept.

I started this because my late summer felt a little stuck, and tools seemed like a manageable place to experiment. The funny part is that the smallest change was the one I kept.

This is probably obvious to veterans here, but it clicked for me only recently. debugging got easier when I stopped treating every attempt like a final exam.

56 sparks · 6 comments

Comments

Miguel Santos · 52 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.

Hope this helps!

Aisha Jacobs · 0 likes

That is a much better way to say it.

Isha Menon · 19 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.

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

Avery Johnson · 4 likes

Fair pushback.

Élodie Favre · 4 likes

Small caveat: context changes the answer a lot.

Kabir Khan · 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.

Hope this helps!