Web Dev · by Diego Quispe · 2026-10-07
What is the kindest way to start with backend in real life?
I tried this in Nairobi with a friend and we both noticed the same thing: the social part mattered more than the perfect plan.
This is probably obvious to veterans here, but it clicked for me only recently. backend got easier when I stopped treating every attempt like a final exam.
53 sparks · 9 comments
Comments
Maja Wiśniewska · 8 likes
Start by reducing it to the smallest reproducible piece, then change one variable at a time. You will learn more from a simple version repeated three times than from a perfect plan you never start.
- 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!
Mateo Cruz · 7 likes
I love this. It feels practical without pretending life is neat. This pairs weirdly well with tacos.
Diego Quispe · 3 likes
Small caveat: context changes the answer a lot.
Mehdi Benali · 6 likes
I had a similar experience, but my problem was consistency rather than motivation. I would test it for 2 days before deciding.
Quiet Fern · 5 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.
Lucas Silva · 2 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.
Source: mostly hard-won experience and comparing notes with people who stuck with it.
Lena Müller · 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. The 8-minute rule is underrated.
Camille Dubois · 0 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.
Source: mostly hard-won experience and comparing notes with people who stuck with it.
Chloe Davis · 4 likes
Exactly; the hidden cost is energy.