4 ms·
Getting a project to the point where it becomes clear that an idea works is one thing. But in my experience getting it polished to the point that other people c
by mr_mitm 2y ago
Getting a project to the point where it becomes clear that an idea works is one thing. But in my experience getting it polished to the point that other people can use it, and writing documentation and ideally test cases with it, and then automating a build pipe line, maintaining versioning and a change log etc., is almost the same amount of work, except much more mundane and without a lot of room for creativity, so a lot less fun. No wonder many people don't like to finish.
- octopoc 2y agoThe only reliable way that I finish my side projects is by using them for something I need to do anyway. If I can use something I made by going slightly out of my way, I get to improve it to completion (at least for the use case I'm doing). But if I have to go significantly out of my way to use it, then it gets abandoned like everything else. That, and I have a tendency to put most of the documentation into a quick overview and really, really detailed error messages. In fact I'll often have quite a bit of code trying to guess what the user's intent was, because that makes things easier for future me.