![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Apparently I'm much more of an optimist than I realize.
I can't say how many times I find a problem in the code, fix it, and expect the fix to work fine, and there not to be any more major issues. Or at least, not until after I've verified the first fix.
Not that I don't know that there might still be other problems, but just that early in the day, I seem to have unbounded *optimism*. The kind of feeling that makes me think, I can test this fix, and then go on to test that other fix my co-worker put in, and then successfully retest the scenario the BA was having problems with, and then maybe even have time to debug the other outstanding issue. Like, I seriously expected I might be able to do all of that today!
It's not supposed to happen that in testing the first fix, I get totally unexpected results, and upon research determine that those results are due to stranded data from yesterday's failed tests, plus additional problems in the error handling logic, plus maybe the cursors needing extra conditions in them, plus who knows what else.
Please, not another can of worms. I've got enough cans of worms already!
*Optimism*, because this code was extensively tested in the past and was working pretty good back then. Even though I should be pessimistic due to all the issues we've already found, which have mainly been due to a large code refactoring project that was done last year.
I can't say how many times I find a problem in the code, fix it, and expect the fix to work fine, and there not to be any more major issues. Or at least, not until after I've verified the first fix.
Not that I don't know that there might still be other problems, but just that early in the day, I seem to have unbounded *optimism*. The kind of feeling that makes me think, I can test this fix, and then go on to test that other fix my co-worker put in, and then successfully retest the scenario the BA was having problems with, and then maybe even have time to debug the other outstanding issue. Like, I seriously expected I might be able to do all of that today!
It's not supposed to happen that in testing the first fix, I get totally unexpected results, and upon research determine that those results are due to stranded data from yesterday's failed tests, plus additional problems in the error handling logic, plus maybe the cursors needing extra conditions in them, plus who knows what else.
Please, not another can of worms. I've got enough cans of worms already!
*Optimism*, because this code was extensively tested in the past and was working pretty good back then. Even though I should be pessimistic due to all the issues we've already found, which have mainly been due to a large code refactoring project that was done last year.