Programming · by Jiho Lee · 2026-09-13

What is the kindest way to start with architecture when life is busy?

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

I tried this in Dublin with a friend and we both noticed the same thing: the social part mattered more than the perfect plan

59 sparks · 14 comments

Comments

Léa Bernard · 12 likes

This reminds me of something a friend in São Paulo mentioned. Honestly, the simplest version wins for me. I would love to see the benchmark numbers

Solar Fern · 11 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. My friend tried it in Mumbai and had the opposite result

Danylo Kovalenko · 4 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 am curious whether debugging still feels good next month

Mateo Cruz · 1 likes

short answer: yes. Long answer: also yes

Valeria López · 3 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I would love to see a follow-up after 6 weeks

Niamh Byrne · 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. Honestly, the simplest version wins for me

Chinedu Adeyemi · 1 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. For me it came down to the routine

Nicolás Díaz · 1 likes

The best answer in the thread, honestly

Isha Menon · 1 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. This is where I would ask one more question before choosing

Oussama Alaoui · 0 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. My friend tried it in Kuala Lumpur and had the opposite result

Haruto Sato · 6 likes

Appreciate the nuance

Tola Ibrahim · 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 would love to see a follow-up after 10 weeks

Isha Menon · 7 likes

Totally agree, especially for beginners

Mara Fischer · 0 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The low-effort version is probably the keeper