Programming · by Liam Eriksson · 2026-09-10
Is there a simple rule of thumb for architecture?
My current rule is simple: if it takes less than 5 minutes to prepare, I am much more likely to keep doing it.
Context: I am not an expert, just someone trying to make Programming feel less intimidating. I wrote down what worked, what felt awkward, and what I would do differently next time.
I know this is a tiny sample size, but after 3 attempts the pattern is pretty clear. When I keep the setup simple, I actually follow through.
38 sparks · 14 comments
Comments
Curious Atlas · 19 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 Madrid example makes it feel concrete.
Maia Brown · 2 likes
I was going to disagree, but your second sentence got me.
Anna Gruber · 0 likes
Respectfully, I see it the other way.
Jack Taylor · 5 likes
I needed the reminder to start smaller.
Lena Müller · 3 likes
@at_fern Kind of wild how often other is the whole issue.
Jiho Lee · 0 likes
Appreciate the nuance.
Jonas Schneider · 6 likes
Good reminder that boring can be good. My only addition is to make the first step visible.
Grace Parker · 1 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.
Lina Keller · 1 likes
This comment has main-character footnote energy.
Sophie Gagnon · 0 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. Honestly, the simplest version wins for me.
Chloe Davis · 1 likes
Respectfully, I see it the other way.