What is a realistic first 8-week plan for java when life is busy?

Sofía Hernández · 11 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

Brian Otieno · 4 likes

Kind of wild how often mysterious is teh whole issue

Solar Sparrow · 1 likes

I had the same reaction to long

Mariam Said · 11 likes

Beautifully concise

Lina Al Harbi · 6 likes

Beautifully concise

Oussama Alaoui · 6 likes

helpful correction

Ren Suzuki · 5 likes

Respectfully, I see it the other way

Brave Atlas · 0 likes

I was going to disagree, but your second sentence got me

Brave Lantern · 0 likes

Appreciate the nuance

Aoi Ito · 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. I learned that one the expensive way

Tiny Atlas · 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. I care less about the perfect answer and more about repeatability

Theo Bennett · 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. The social part surprised me too

Mango Rider · 9 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 winter version is even more interesting

Solar Lantern · 8 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. My friend tried it in Cape Town and had the opposite result

Silver Runner · 7 likes

That is a surprisingly elegant way to frame it. I would love to see a follow-up after 2 weeks

Arif Hasan · 11 likes

I am curious what changed your mind

Rafael Almeida · 6 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 care less about the perfect answer and more about repeatability

Can Arslan · 13 likes

I was going to disagree, but your second sentence got me

Noah Meier · 0 likes

I had the same reaction to care

Emir Kaya · 5 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. For me it came down to the practice run

Ananya Rao · 8 likes

I would pin this if I could

Brian Otieno · 4 likes

The plan angle is what sold me. The practical constraint is probly the real story

Noé Petit · 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 debugging still feels good next month

Isha Menon · 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. Honestly, the simplest version wins for me

Sleepy Mango · 0 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. This would have saved me a lot of trial and error

Sleepy Marauder · 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 the kind of detail beginners miss