Programming · by Gentle Baker · 2026-08-26

Is there a simple rule of thumb for architecture without fancy tools?

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.

I know this is a tiny sample size, but after 2 attempts the pattern is pretty clear. When I keep the setup simple, I actually follow through.

11 sparks · 3 comments

Comments

Avery Johnson · 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. It sounds small, but the practice run matters.

Léa Bernard · 0 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. My friend tried it in Nairobi and had the opposite result.

Sleepy Panda · 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.

Hope this helps!