Programming · by Beatriz Sousa · 2026-09-28
How would you solve this late summer problem with java with limited time?
> Tiny progress is still progress.
That line sounds cheesy but it got me thru the part where architecture stopped feeling new.
My current rule is simple: if it takes less than 3 minutes to prepare, I am much more likely to keep doing it
50 sparks · 11 comments
Comments
Kabir Khan · 14 likes
I wish more posts had this much context. A little friction removed goes a long way
Mango Noodle · 13 likes
I was going to disagree, but your second sentence got me
Sofía Hernández · 11 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 low-effort version is probably the keeper
Maja Wiśniewska · 6 likes
the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I noticed the same thing in Manila
Narin Chai · 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. The social part surprised me too
Hugo Martin · 0 likes
Thanks for making it less intimidating
Maya Williams · 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. It reminds me of a very specific conversation near a neighborhood park
Rapid Baker · 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. This is more useful on a tired busy month then on a perfect day
Sara Hosseini · 0 likes
Can you share what you tried before this? I noticed the same thing in Toronto