| I feel you...this describes a lot of my github. I find I burn out after I get the fun technical part done and it's a viable proof of concept. The polishing going to release it to others is a high burden. I recently have been building something that in passionate about with a level of polish that is not typical. Here are some pointers from that experience and some of the others I actually got into the hands of other people. All depends on your motivations but here are some things I think drove me (outside of work hobby development) 1) find something you are passionate about or that solves a problem for you or people you care about 2) "don't try to boil the ocean", sounds like you are already trying to scope your projects well, but really focus on the smallest minimum viable initial product you can get into the hands of others for feedback..... 3) find users or some external force driving you to finish. It helps me when I have some constraint on time that drives progress. User feedback and showing your work to someone is incredibly motivating. 4) find the part you usually burn out on. For me it getting the interesting part database backed with a web GUI. I always joked the perfect UI was command line, but for many users it's not. I found a tech stack that I am productive in and enjoy writing in (Refine.dev,Supabase). I had tried for years to find something that stuck...all the way back to when rails was the new hotness. 5) Automate work flows so working on your project does not involve slogging through manual processes. CI/CD is pretty easy to set up these days with GitHub actions, netlify, fly.io etc. 6) find ways to integrate stuff you read about on hacker news or other sites into your project. Use it as a sandbox for testing out new technologies you read about. 7) chatGPT...some of my least favorite parts of a project, chat gpt has made immeasurably easier. This resource is truly game changing, helping my productivity and letting me quickly prototype new functionality. |