2 ms·
When a programming project starts to become this endless chore that I progressively look less forward to the more I work on it, that's when I know it's time to
by 65 5y ago
When a programming project starts to become this endless chore that I progressively look less forward to the more I work on it, that's when I know it's time to take a step back and ask myself why I am even doing this in the first place.
Am I making this app just so I can try to make money on it, for something to put on my resume? Or am I doing it as a nice way to spend my evening? What's the point of free time if you don't enjoy it?
Not every project needs to be some kind of profitable SaaS or wildly popular open source tool. It's fun to research and experiment and take a step back every once in a while and ask yourself why you're even doing this.
Once it turns into a business, sure that can be fun, but you have to ask yourself -- do I even look forward to this? Is this even enjoyable? This is my free time, after all.
I write code for both work and for fun. It's important for me to like my job. I don't want to spend most of my waking life toiling away at something I don't at least like to do. I also want to like my creative pursuits in my free time. If you don't enjoy doing something, why do it at all? Especially when you have the choice to do other, more enjoyable things.
- vshan 5y agoThe weed work is the most painful though. We get through it at work because we have to. But for any personal hobby projects, I feel nails scraping blackboard level of frustration when some build issue or other trivial minutiae come up.