I hate it when I'm right.
May. 14th, 2008 07:30 pm*Weeks* ago I saw a small detail in some code I was working on, a piddling little implementation point that made me go "hmmm... that doesn't look particularly clean."
But, it was a single call, on a single line, in a single file, out of a few gazillion such things, and it wasn't causing issues at the time.
Guess what came boomeranging back to bite me on the ass? As soon as I saw the call point in the stack trace, I knew what the issue was.
Workaround in progress, since of course I planned out a contingency in case this happened. (I can't help it - I see a pain point in the code, I design new code... even if I never implement it. I have mental designs on how to fix code I haven't touched in *years*, literally. Fourteen years, in one case. I never know when I might dust it off and find it useful, you see, but I rarely have time to implement the fixes unless I *need* to.)
Good thing I have plans in place for the other unclean points in the code... :D
But, it was a single call, on a single line, in a single file, out of a few gazillion such things, and it wasn't causing issues at the time.
Guess what came boomeranging back to bite me on the ass? As soon as I saw the call point in the stack trace, I knew what the issue was.
Workaround in progress, since of course I planned out a contingency in case this happened. (I can't help it - I see a pain point in the code, I design new code... even if I never implement it. I have mental designs on how to fix code I haven't touched in *years*, literally. Fourteen years, in one case. I never know when I might dust it off and find it useful, you see, but I rarely have time to implement the fixes unless I *need* to.)
Good thing I have plans in place for the other unclean points in the code... :D