Programming · by Benjamín Rojas · 2026-09-12
Which advice about learning did you eventually ignore with limited time?
The detail that surprised me was how much the library changed the outcome. Same plan, different setting, completely different energy.
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.
> Tiny progress is still progress.
That line sounds cheesy, but it got me through the part where java stopped feeling new.
17 sparks · 14 comments
Comments
Jasmine Cruz · 3 likes
Beautifully put. I needed that reminder today. It sounds small, but the conversation matters. This is exactly the kind of tradeoff teams argue about for weeks.
Élodie Favre · 1 likes
@marauderPixel75 Adding this to my notes.
Jan Nowak · 0 likes
Kind of wild how often exactly is the whole issue.
Tola Ibrahim · 3 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I care less about the perfect answer and more about repeatability.
Noah Miller · 2 likes
Not wrong, but I think this underestimates how different people's constraints are. Honestly, the simplest version wins for me.
Piotr Zieliński · 2 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. I am curious whether learning still feels good next month.
Benjamín Rojas · 1 likes
Love the tiny experiment energy. I would love to see a follow-up after 3 weeks. Naming things remains undefeated as the hardest problem.
Nicolás Díaz · 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. A little friction removed goes a long way.
Maya Williams · 1 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. The useful part is easy to underestimate.
Nour Ali · 0 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. That is where the boring checklist helps.
Amelia Hughes · 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. The rainy evening version is even more interesting.
Urban Fern · 0 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. This pairs weirdly well with arepas.