Programming · by Liam Eriksson · 2026-10-09
What mistake taught you the most about learning without overthinking it?
context: I am not an expert, just someone trying to make Programming feel less intimidating. I wrote down what worked, what felt awkward, and what I would do differently next time.
My current rule is simple: if it takes less than 3 minutes to prepare, I am much more likely to keep doing it
39 sparks · 9 comments
Comments
Ethan Brooks · 15 likes
Good reminder that boring can be good. The the kitchen detail changes the whole answer. Good reminder that tools should serve people, not the reverse
Antonia Silva · 4 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. This would have saved me a lot of trial and error
Lina Al Harbi · 5 likes
Kind of wild how often visible is the whole issue
Léa Bernard · 0 likes
Totally agree, especially for beginners
Quiet Noodle · 2 likes
This has cozy competence written all over it. The cozy constraint is probly the real story. The boring solution is probably the reliable one here
Minji Kim · 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 used to overcomplicate this constantly
Priya Nair · 0 likes
Kind of wild how often found is the whole issue
Ren Suzuki · 0 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