Web Dev · by Mariana Costa · 2026-09-25
How do you get better at backend without burning out in real life?
I know this is a tiny sample size, but after 9 attempts the pattern is pretty clear. When I keep the setup simple, I actually follow through.
I had a disappointing first try, a surprisingly good second try, and then a third attempt that taught me humility. So, naturally, I now have opinions.
58 sparks · 7 comments
Comments
Liam Wilson · 24 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 only addition is to make the first step visible.
Lina Al Harbi · 6 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.
Source: mostly hard-won experience and comparing notes with people who stuck with it.
Noah Miller · 4 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The Lisbon example makes it feel concrete.
Paolo Garcia · 1 likes
Start by reducing it to the smallest reproducible piece, then change one variable at a time. If two options look equal, choose the one that is easier to reverse.
- 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.