Spot on. I've been saying for years "programming is not hard, we make it hard". But yes, I run into this same problem from time to time, I try and do too much at once, and it rarely works. Even if we can understand the complexity, what happens when we make mistakes in our boolean logic in multiple spots? Sometimes that's hard to spot without a debugger. And yet we wouldn't even need the debugger if we'd stayed small.
« you think of a new test that will likely fail » I see why other reasons are sign to have a break but thinking about a test that will fail is part of the process to me.
Or is it because I think about it instead of writing it ?
Or is it because of the "likely" which means I'm not sure ?
For me to do it at all, I need to keep it easy. Good advice here - Thanks!
Keen to play the index card game.
Spot on. I've been saying for years "programming is not hard, we make it hard". But yes, I run into this same problem from time to time, I try and do too much at once, and it rarely works. Even if we can understand the complexity, what happens when we make mistakes in our boolean logic in multiple spots? Sometimes that's hard to spot without a debugger. And yet we wouldn't even need the debugger if we'd stayed small.
« you think of a new test that will likely fail » I see why other reasons are sign to have a break but thinking about a test that will fail is part of the process to me.
Or is it because I think about it instead of writing it ?
Or is it because of the "likely" which means I'm not sure ?
So much yes!