NolanRollen

Right on. Good luck with your project.

Thank you

I'm pretty happy with my linux on that front.

I've tried linux. I've never goten used to the feel of it though.

I break my projects out into phases

1. R&D
   1. Research and development
   2. This is a proof of concept experimentation phase, coming out of this I should have a general idea if the project is possible, what I want to get out of my first milestone and should have a general idea of how I'm going to architect it
   3. If looking for feedback, develop mock ups and present those
2. Pre-alpha
   1. Actually programming. In this state there isn't enough for anyone to test and feedback isn't worth anything to you yet.
3. Alpha
   1. You're in the infancy stages of your application. It's large enough and has enough features that additional testing and feedback is valuable. At this point you'd invite trusted people to test your application IF it's too much for you to test or you need feedback.
   2. New features are still being developed
4. Beta
   1. All "new features" are complete. The only thing left to do before release are fix outstanding bugs and very minor improvements or small UI changes.
5. Release
   1. All known bugs fixed, everything working as intended.

 

So, "when" is really a matter of when you need it. Collecting feedback too late in the project can set you back, but too early on and the feedback will be worthless. So, more or less when the software is in a usable state and something at least some people would want to use.

Thank you. I've havent had shared my projects with anyone yet so I figured that i should. Thanks for the tip! I appreciate it!