When you are learning, you write a lot of code that with experience you no longer admire. That just proves how far you have progressed. The "second system eff

When you are learning, you write a lot of code that with experience you no longer admire. That just proves how far you have progressed. The "second system effect" suggests that the rewrite will take a great deal of effort and for very little gain. If I were in your position, I would direct my energies to new projects. There is far greater potential for expanding your experience and knowledge than by reworking something that you will shudder to look into too deeply. As for my experience. I have shelved my early systems. For systems I wrote in the past 10 years, I have been refactoring every time I add a new feature or fix some edge case. By maintaining clean separation of concerns it has even been possible to swap out one module implementation with another.