Shorter, simpler code is much easier to read, interpret (how is it doing what) and debug
I know a technical text / code is easier to read with a introduction / declarations. looking at a declaration of method in java tells you a lot. and you do not even need to follow the code!
I've found that the ability to write very terse code goes a long way to reducing time spent debugging
I found exactly the opposite. writing tests , splitting code into more smaller functions, using descriptive names thus writing more code reduces debugging time for me
Frankly I can't afford to spend half a day debugging if I can avoid it.
I agree. And that is a good reason to use java. You will type a lot more but debug less.
by grrr — Mar 01
I know a technical text / code is easier to read with a introduction / declarations. looking at a declaration of method in java tells you a lot. and you do not even need to follow the code!
I found exactly the opposite. writing tests , splitting code into more smaller functions, using descriptive names thus writing more code reduces debugging time for me
I agree. And that is a good reason to use java. You will type a lot more but debug less.