Is there a simple rule of thumb for java with limited time?

Noah Miller · 15 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.

Source: mostly hard-won experience and comparing notes with people who stuck with it.

Maia Brown · 1 likes

Exactly; the hidden cost is energy.

Noah Miller · 3 likes

That is a good boundary.

Haruto Sato · 0 likes

Kind of wild how often version is the whole issue.

Tanvir Rahman · 10 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 routine.

Tola Ibrahim · 5 likes

The kindness in this post is lovely. The Monday morning version is even more interesting. This is exactly the kind of tradeoff teams argue about for weeks.

Brave Orbit · 3 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.

Source: mostly hard-won experience and comparing notes with people who stuck with it.

Maya Williams · 3 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 7-minute rule is underrated.

Bianca Santos · 2 likes

I am cheering for this update. I would write it down before changing anything else. The boring solution is probably the reliable one here.

Mango Panda · 5 likes

@riderNomad9 Could be regional too.

Noah Miller · 5 likes

Thanks, that actually helped.

Ananya Rao · 2 likes

Noted, and thank you.

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. I noticed the same thing in Kuala Lumpur.