What mistake taught you the most about java with limited time?

Isha Menon · 11 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. My friend tried it in Warsaw and had the opposite result

Youssef Mahmoud · 3 likes

The safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. The 9-minute rule is underrated

Nusrat Akter · 7 likes

I think both things can be true

Tiny Comet · 0 likes

I am stealing that phrase

Mina Chowdhury · 2 likes

the safe answer is to keep the API boring: clear names, explicit errors and one behavior per function. I would test it for 4 days before deciding

Noah Johansson · 3 likes

anecdote beats theory here

Diego Quispe · 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 delightful constraint is probly the real story