What GfK said. software Engineers have been struggling with this problem for ages, and have developed two principles to remember, which will help you deal with the issue.
The first issue is the "Good enough is best" principle which states that when you get an idea for an improvement, you should balance that idea against whether the existing implementation is good enough. If it is, there is no need to rewrite it.
The second one, which is related to the first one, but more specific to generalization and new features is known as the "You're never gonna need it" principle. The gist of it is that unless you absolutely must have said feature or generalization, because it would solve a real, current problem odds are good you're never going to need it, so doing it is pointless.
The first issue is the "Good enough is best" principle which states that when you get an idea for an improvement, you should balance that idea against whether the existing implementation is good enough. If it is, there is no need to rewrite it.
The second one, which is related to the first one, but more specific to generalization and new features is known as the "You're never gonna need it" principle. The gist of it is that unless you absolutely must have said feature or generalization, because it would solve a real, current problem odds are good you're never going to need it, so doing it is pointless.