I think part of my problem is that I am obsessed with the program, and keep finding things that can be improved, or new features that can be added, all of which takes time. That is my problem that I have to figure out how to deal with.
But then there is the support. Sometimes I just get stupid people that don’t know what the heck they are doing asking questions or saying they are getting an error and it is not working. Then sometimes I get smart people that just don’t read the user manual first, and ask questions that they should have figured out on their own. But then there are the times where it turns out to be some sort of issue or bug that I need to (or should) address, or maybe something that I just can’t fix without having the problem hardware myself.
My goal is to get the program to the point where there are few or no bugs. My ideal goal is to just be able to sell it and not have to deal with any issues (pipe dream?). I think I am sabotaging myself in a way by adding extra features and improvement that could cause bugs that I have to deal with. And here I am about to release a major new feature, just waiting for someone to find something wrong with, or not understand it. Maybe I just need to adjust how I deal with support, and say “this is my software, and it is what it is, you can report bugs, but otherwise just deal with it”. That is not a good attitude for customer service, but I might have to adopt it to some point to free myself. The problem is how to do that without blowing off actual potential bug issues. Sometimes it is difficult to tell the difference.
Even though not many have purchased it, I still do like the bit of extra income

I just need to not spend as much time on it. That would mean less support and bug fixes. Still not sure where I am with this overall.
_________________
http://www.sdcomputingservice.comHome of HDDSuperClone and HDDSuperTool