> I have tests but changing existing behaviors feels exhausting. Tests freeze your design and purposely makes big architectural changes difficult. This is why

> I have tests but changing existing behaviors feels exhausting. Tests freeze your design and purposely makes big architectural changes difficult. This is why they're so good/important for libraries, services, and finished products because you don't want to break things for the clients. If this side project is supposed to fun then why bog yourself down with that ceremony. Put the tests aside and just do what needs to be done to get it finished. I used to have a similar problem finishing and deploying projects. My projects now go through 3 stages: 1. The initial fooling around and figuring out the product -- this is the funnest part of the project. 2. Taking that initial mess and turning it into something end-user viable to use. I try and decide before starting this part the minimal viable feature set. Sometimes this involves designing the UI and resisting the urge to add more to it later. 3. Deployment. I stop working on the project as it's own thing. Instead it's now "done" and this is a new project dedicated to getting that other one out. This might involve writing documentation, creating web pages, installers, etc. By making this a separate in my mind, it helps make it happen. I'm currently on stage 3 on one of my personal projects and I hope to get it out next week. I finished stage 2 several weeks ago and it's taken until recently to get back to it.