It's been well said here already but side projects can be so different. Some are for learning, some are for trying out certain approaches, and some are really

It's been well said here already but side projects can be so different. Some are for learning, some are for trying out certain approaches, and some are really to find out if it's a good day to go to a park. While it's good to "finish" something, maybe there's an earlier start line, or finishing point you can release, and continue to add to? Sometimes launching can be it's own feedback loop, if you were going to put in. If it's a side project, unless you're learning testing, do you want to skip some of that? Might just be overdoing it in terms of novelty per feature. Depending on the personal project, I sometimes will only do tests on the most complex or sensitive parts first. If I can't fetch data from a database by this point... On the other hand if it was for something professional in the future, maybe I'd want to pay more attention to it. The fun with personal projects is you don't have to do everything right, you can do it all wrong, because it's up to you and for you. If it's a side project for others, sometimes the simpler approach with a boring tech can be surprisingly sturdy. I rewrote something last week, and when deciding to do it in JS or Python, I shrugged and picked python because it could play with something else I was going to try out later. If I thought about it another way I'm sure I could have done it in JS too. Luckily the technologies can often call each other. In any event, I try to find good stopping points so it's easier to pick up, or start what I can easily finish in one sitting, and maybe thinking about the next step before I walk away to come back to that.