My original motivation for starting it got lost somewhere along the way by getting swayed amidst the various user requests. I lost the sense of priority, and felt like I was working to please some imaginary crowd, rather than remaining focused on that original motivation.
The solution was simply to undo that transition, by rememorating the original motivation and then codifying it (what the author calls setting of project goals). This enables me to keep on track, with zero anxiety about rejecting / ignoring user requests if they are not relevant to the goals at the moment.
And the author’s realization has clearly worked for them, given the success of their open-source portfolio (Haskell libraries and tools): https://github.com/kowainik
I’ve come to a similar conclusion for my project.
My original motivation for starting it got lost somewhere along the way by getting swayed amidst the various user requests. I lost the sense of priority, and felt like I was working to please some imaginary crowd, rather than remaining focused on that original motivation.
The solution was simply to undo that transition, by rememorating the original motivation and then codifying it (what the author calls setting of project goals). This enables me to keep on track, with zero anxiety about rejecting / ignoring user requests if they are not relevant to the goals at the moment.
And the author’s realization has clearly worked for them, given the success of their open-source portfolio (Haskell libraries and tools): https://github.com/kowainik