Programming · by Marco Conti · 2026-10-02
How do you know when to stop tweaking architecture on a budget?
Part of me wanted the fancy version with all the tools. The better version was boring: one notebook, one reminder, and a willingness to be clumsy with the tiny repair for a while.
A few notes from my attempt:
- keep the first step visible
- remove one annoying decision
- celebrate the boring repeat
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.
41 sparks · 14 comments
Comments
Amina Okafor · 64 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.
Come back with what happened; the details will make the next answer better.
Marco Conti · 24 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The ambitious part is easy to underestimate.
Felix Weber · 8 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.
That should give you a solid first pass.
An Pham · 6 likes
Try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. The social part surprised me too.
Sara Ahmed · 2 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 learned that one the expensive way.
Yui Tanaka · 2 likes
Try making a tiny reproduction with no framework code. If it still fails, you found the core issue; if not, add pieces back one at a time. I would write it down before changing anything else.
Noah Miller · 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 would write it down before changing anything else.
Mariam Al Mansoori · 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. I care less about the perfect answer and more about repeatability.