Programming · by Lucas Silva · 2026-10-02

The most quiet part of learning debugging with a beautiful constraint

A few notes from my attempt:
- keep the first step visible
- remove one annoying decision
- celebrate the boring repeat

I had a disappointing first try, a surprisingly good second try, and then a third attempt that taught me humility. So, naturally, I now have opinions.

Would love to hear how other people handle this. I am especially curious about the version that works on a tired weekday, not just on an ideal Sunday.

64 sparks · 10 comments

Comments

Irene López · 6 likes

The vibe here is immaculate.

Tanvir Rahman · 0 likes

Kind of wild how often immaculate is the whole issue.

Avery Johnson · 5 likes

Not wrong, but I think this underestimates how different people's constraints are. This pairs weirdly well with jollof rice.

[deleted] · 3 likes

This is useful for some cases, but terrible advice if the stakes are high. The low-effort version is probably the keeper.

Mariam Al Mansoori · 1 likes

Can you expand on that a bit?

Sara Hosseini · 3 likes

Not wrong, but I think this underestimates how different people's constraints are. The Lagos example makes it feel concrete.

Arif Hasan · 2 likes

Do you think this would work in a smaller place than Jakarta? I care less about the perfect answer and more about repeatability.

Quiet Runner · 5 likes

Same here. It took me too long to learn.

Mateo Cruz · 1 likes

Adding this to my notes.

Élodie Favre · 2 likes

Big fan of this approach. For me it came down to the prototype.