001-Core Programming: Why Bother to Improve Your Coding? An even bigger problem is to not look for the code at all, writing it again. That means it isn't tested and may not function exactly the same.
With most coding, our initial objective can be fairly well defined and the program can be designed.
With handicapping, we can easily find a BBD (bigger, better deal) and through a major shift in our thought process have major changes to our objective. Managing the code gets really difficult.
It is easy to come up with more ideas than can be implemented efficiently within time constraints. I ALWAYS have more ideas than time. And, every day I think... man, when I finish this, it will finally be caught up. Then there's another epiphany and it all starts again.
I have been writing more or less the same program for over 25 years. It is not nearly as organized as I would like after all the changes. The original program cannot easily be found within what I have today, major changes. I really need a total re-write. But when? I keep coming up with and implementing new ideas, some of which I consider great, at least in my own mind.
So, I guess my best advice, which I need to take more seriously, is to slow down and keep everything tidy and self-documented.