I’ve become worse at programming
I&#x27;m not sure whether the author wants to find the motivation to continue or the will to stop.<p>This article is frustration embodied, and I <i>completely</i> empathize, having been in a very similar situation with a large and long running project that had many (thousands of) users. Motivation and enjoyment comes and goes, but I couldn&#x27;t bring myself to stop doing it because of the effort it took to get there, and because people were using it and counting on it&#x27;s continued development.<p>The author is sad and tired and can&#x27;t see the big picture. It&#x27;s extremely unlikely he&#x27;s getting worse at programming, unless he works really hard not to learn from this -- but this article is evidence he&#x27;s already learning what happens to big projects. You have to acknowledge what&#x27;s going on (done) and then step back and think about how to improve the situation.<p>I&#x27;m not sure how to find the motivation to continue, if that&#x27;s what he really wants. But at least take a solid break and then spend some non-dev time re-evaluating what&#x27;s important and where you&#x27;re headed. Consider whether continuing solo is a goal, or whether recruiting real partners might be what both you and the project really need. Ask what success looks like.<p>As for permission to quit, it&#x27;s not true that giving up is a massive loss of work. All the work done is already done. Lily runs, and lessons have been learned. The code isn&#x27;t going anywhere. You can walk away from this and you get to keep everything you ever put in. What you lose by quitting is future potential, not the sunk cost. So if you want to quit and the only thing holding you back is fear or sunk cost -- go ahead and quit, sunk cost is imaginary in this case.