Programming · by Élodie Favre · 2026-09-12
What mistake taught you the most about java in real life?
My current rule is simple: if it takes less than 7 minutes to prepare, I am much more likely to keep doing it.
I had a disappointing first try, a surprisingly good second try, and then a third attempt that taught me humility. So, naturally, I now have opinions.
44 sparks · 28 comments
Comments
Sleepy Runner · 22 likes
Start by reducing it to the smallest reproducible piece, then change one variable at a time. You will learn more from a simple version repeated three times than from a perfect plan you never start.
- Write down the exact error and the input that caused it.
- Make a tiny example, then add pieces back slowly.
- Keep the final fix boring and well-named.
That should give you a solid first pass.
Emma Tremblay · 2 likes
Small caveat: context changes the answer a lot.
João Pereira · 12 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 love to see a follow-up after 7 weeks.
Jack Taylor · 12 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. This pairs weirdly well with tacos.
Paper Panda · 10 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. Honestly, the simplest version wins for me.
Nour Ali · 6 likes
Beautifully put. I needed that reminder today. The Cape Town example makes it feel concrete.
Grace Parker · 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.
Priya Nair · 4 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I used to overcomplicate this constantly.
Jack Taylor · 2 likes
The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. My friend tried it in Lagos and had the opposite result.
Irene López · 0 likes
This is the kind of disagreement I like.
Élodie Favre · 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. This is where I would ask one more question before choosing.
Tiny Runner · 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 a neighborhood park detail changes the whole answer.
Noah Miller · 1 likes
Did anyone else read this and immediately make a tiny checklist? I would write it down before changing anything else.
Kabir Khan · 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. A little friction removed goes a long way.
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. I would test it for 9 days before deciding.