[bbarthel]

"Don't view getting a job as failing. "

I was actually going to post this exact same advice. Getting a job is not failing. You graduated college so obviously you place some value in having a structured environment to learn. If done carefully, a good job can provide you with a whole new set of skills (and contacts) that may prove invaluable, in much the same way college did - only you are getting paid for it and building up that independence. On top of that, you can still work on your project - it is not one or the other.

Also, I actually believe that learning how to release is very important. A good job will teach you that skill. How do you decide what is the "minimum" set of features? How do you decide which bugs have to be fixed and which can be ignored for now? How do you decide when a feature is "complete"? How do you balance the need for a new release yesterday versus the need to address issues and add value. These are all things that it sounds like you are having trouble with - and a good job will show you how other people make these decisions, which you can then apply to your own project.