Something to think about at the bottom, but long ass post post. If you reply TL;DR I care less than you want to know. this only takes a couple of minutes to read.
You're entitled to your opinion about CIG, and Star Citizen. I am also entitled to mine, and that is, If you can't take the heat, maybe you should think about backing away from the fire a little. If you don't like testing alpha software, or don't care to learn what the term means, then don't test it. Walk away, and come back when the software is released.
If I just told you I think you need to walk away from Star Citizen for a while, skip down to the last two small paragraphs under the line of asterisks, or stop reading. Your choice. If you're interested in the process, but find yourself frustrated then please read on.
Software design and development are very complex tasks, indeed it is among the most complex things that humans as a species will ever engage in. Because of the complexity, there is a very high possibility that things will go wrong. To mitigate against this, developers have implemented a series of best practices designed to identify what is going wrong. As part of this, is dividing the software development into phases. In large projects, there are three distinct phases of development, identified by a test of that phase:
- Alpha software is software that is both incomplete, and untested. At some point, the developer wants to identify where issues are in the software that they have, and get feedback on the direction they've taken, and quite honestly they can't do it on their own. So, they start an alpha trial or alpha test.
- The primary goals of alpha trials is to work out where hidden bugs are that didn't show up during development, where things aren't working properly, and what can potentially be implemented better.
- As modules are added to the software, alpha testing is repeated. Wash, Rinse Repeat.
- After successful alpha trials (which may require several test cycles known as alpha builds), the software is moved into a beta phase, which means that its individual components have been tested, but now the software needs to be tested as a whole. All the desired functionality is in place, and everything has been individually tested. Developer confidence in each module is relatively high at this point, but low for the overall system.
- Any new problems with the way that the software is working can be fixed, and new beta builds can be released during the beta trial period.
- But if any new functionality is added to the software after beta trials have started, the software goes back to Alpha, and requires successful alpha trials of the new functionality before beta trials can continue.
- The final stage of software development is the release candidate. These are builds where everything has been included, and fully tested. The developer's confidence is high that everything is working as designed.
- The focus now changes to "does the software work as desired".
- If so, the development process for that release ends, and the software is released.
- If not, the deficiency is identified, and fixed, and the software is put into beta trials. If successful another release candidate is identified, and this process continues until it a release candidate is accepted.
Just for your information, generally the more complex a piece of software, the longer this process takes.
Pressure from stakeholders, on the project's management team to short circuit this process is the number one reason why software projects fail.
**********************
Now, When Chris Roberts started this process, he said something to the effect that because this is a player funded game, CIG would follow an open development process, and give backers access to the alpha releases so that we can follow and participate in the development. That means specifically you are going to have the opportunity to see the result of alpha code, in all it's glory.
This is a departure from the safe, secure standard development model in which software goes through alpha and beta testing in a closed and secret environment. Very limited numbers of the user community are only exposed to the final stages of beta testing, and this only once a release candidate version has been identified. The reason CIG is doing this is that they want to build the game WE want, and not just what Chris Roberts wants. That's actually a noble cause. Just for fun, tell a company like Blizzard what you want in a game, and see what you get back.