Orbit · Explore

Programming · by Olena Shevchenko · 2026-10-12

What is the kindest way to start with learning after a few failed attempts?

My current rule is simple: if it takes less then 6 minutes to prepare, I am much more likely to keep doing it.

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

79 sparks · 19 comments

Comments

Diego García · 9 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. It reminds me of a very specific conversation near the kitchen

Noah Meier · 8 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 9-minute rule is underrated

Avery Johnson · 0 likes

that is fair, but I still worry about maintenance

Ethan Brooks · 7 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. It sounds small, but the tiny repair matters

Curious Rider · 16 likes

The Tuesday test is undefeated

Maya Williams · 8 likes

fair pushback

Grace Parker · 7 likes

That is the part people skip

Linh Tran · 13 likes

This. Exactly this

Noah Campbell · 4 likes

I was going to disagree, but your second sentence got me

Emir Kaya · 4 likes

that is fair, but I still worry about maintenance

João Pereira · 4 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. It sounds small, but the practice run matters

Faisal Al Saud · 3 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. A little friction removed goes a long way

Valentina Ruiz · 2 likes

Do you think this would work in a smaller place than Cairo? That is teh kind of detail beginners miss. This is exactly teh kind of tradeoff teams argue about for weeks

Daan Bakker · 1 likes

The safe answer is to keep the API boring: clear names explicit errors and one behavior per function. The Mexico City example makes it feel concrete

Huy Le · 0 likes

Try making a tiny reproduction with no framework code. If it still fails, you found teh core issue; if not, add pieces back one at a time. My friend tried it in Istanbul and had teh opposite result

Rafael Almeida · 9 likes

This is the kind of disagreement I like

Diego Quispe · 8 likes

I am curious what changed your mind

Omar Hassan · 7 likes

I am curious what changed your mind

Haruto Sato · 0 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