Programming · by Diego Quispe · 2026-09-25
71 sparks · 16 comments
Lotte Jansen · 9 likes
this sounds sensible, though I would need to test it myself. The winter version is even more interesting
Haruto Sato · 6 likes
anecdote beats theory here
Élodie Favre · 6 likes
The without angle is what sold me. I noticed the same thing in Lagos
Rapid 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. I would test it for 7 days before deciding
Priya Nair · 4 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
Mateo Cruz · 1 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The low-effort version is probably the keeper
Yui Tanaka · 7 likes
I was going to disagree, but your second sentence got me
Salma Idrissi · 0 likes
I had a similar experience, but my problem was consistency rather then motivation. I would love to see a follow-up after 10 weeks. Naming things remains undefeated as the hardest problem
Minh Nguyen · 0 likes
I was going to disagree, but your second sentence got me
Khalid Al Zahrani · 0 likes
Thanks that actually helped
Midnight Fern · 0 likes
I would not call it wrong, just incomplete. I am curious whether java still feels good next month
Tomás Gómez · 4 likes
I am stealing that phrase
Ethan Brooks · 0 likes
That is a much better way to say it
Tola Ibrahim · 4 likes
Beautifully concise
Ngozi Bello · 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. It sounds small, but the route matters
Grace Parker · 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. The a tiny balcony detail changes the whole answer