What mistake taught you the most about backend without overthinking it?

Daan Bakker · 6 likes

I like the idea, but the setup probably matters a lot

Mango Sparrow · 6 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. This is more useful on a tired commute than on a perfect day

Valeria López · 0 likes

Thanks that actually helped

Lucas Dubois · 6 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. For me it came down to the tiny repair

Ethan Brooks · 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 would love to see a follow-up after 4 weeks

Valentina Ruiz · 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 would write it down before changing anything else

Aoife Murphy · 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 backend still feels good next month

Maja Wiśniewska · 3 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. That is where the boring checklist helps

Cozy Noodle · 2 likes

the safe answer is to keep the API boring: clear names explicit errors and one behavior per function. I used to overcomplicate this constantly

Paper River · 1 likes

short answer: yes. Long answer: also yes

Achieng Njeri · 2 likes

This is the gentle version of my rant

Imogen Clarke · 2 likes

I would log teh input teh expected output and teh actual output first. Once those three are visible, teh bug usually stops feeling mysterious. The practical part is easy to underestimate

Silver Orbit · 2 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I keep a note about performance for exactly this reason

Maksym Bondar · 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. That is where the boring checklist helps

Maya Putri · 1 likes

What happened after the first week? I am curious whether backend stayed easy. For me it came down to the tiny repair. I would love to see the benchmark numbers

Elif Yılmaz · 13 likes

Respectfully, I see it the other way

Siti Lim · 5 likes

Beautifully concise

Liam Wilson · 1 likes

fair pushback

Ren Suzuki · 9 likes

Appreciate the nuance

Theo Bennett · 1 likes

fair pushback

Mariana Costa · 2 likes

Totally agree, especially for beginners

Solar Baker · 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. I learned that one the expensive way

Arif Hasan · 0 likes

This feels a little overrated to me, even if the intention is good. The 2-minute rule is underrated