Programming · by Ngozi Bello · 2026-10-04
What is worth spending money on for architecture when life is busy?
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 conversation for a while.
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.
4 sparks · 5 comments
Comments
João Pereira · 6 likes
Fair point, but I had the opposite experience. The lunch break version is even more interesting.
Lina Keller · 1 likes
Small caveat: context changes the answer a lot.
Brave Panda · 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.
That should give you a solid first pass.
Cozy Noodle · 0 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.
Ayesha Khan · 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. The social part surprised me too.