Programming · by Paolo Garcia · 2026-09-14
Can someone explain the practical difference between tools and the tiny repair in real life?
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.
I tried this in Madrid with a friend and we both noticed the same thing: the social part mattered more than the perfect plan.
9 sparks · 6 comments
Comments
Rohan Mehta · 2 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.
Tiago Costa · 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 Manila example makes it feel concrete.
Camila Rocha · 0 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. A little friction removed goes a long way.