I had this problem myself. My solution: focus on agile, feature-driven development. Make the next feature work in a scrappy (ie exploratory coding) way, then ta

I had this problem myself. My solution: focus on agile, feature-driven development. Make the next feature work in a scrappy (ie exploratory coding) way, then take what you learned and refactor. Don't take it as an opportunity to refactor everything - just the code around that one feature, and close relatives e.g. common functionality that can be abstracted out. Presumably you're working on your software for a reason - not just to press keys for hours on end. So focus on getting the software ready to fulfil that purpose and don't get so caught up on software engineering practices. Most best practices in software engineering are solely there to allow large teams to work on a single codebase anyway (especially so for extensibility and modularity) and that doesn't apply to your project so why would you follow them?