Web Dev · by Liam Eriksson · 2026-09-05

Which advice about backend did you eventually ignore in real life?

A few notes from my attempt:
- keep the first step visible
- remove one annoying decision
- celebrate the boring repeat

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

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.

8 sparks · 4 comments

Comments

Pablo Martín · 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. My friend tried it in Melbourne and had the opposite result.

Brave Atlas · 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.

Hope this helps!

Ayesha Khan · 0 likes

My wallet felt that.

Priya Nair · 0 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.

Come back with what happened; the details will make the next answer better.