Zo eindelijk een stukje over de "release now, patch later" filosofie die we tegenwoordig veels te veel zien.Recently, there has been a rash of games coming out with a new type of philosophy. Most of us know it as, "Release now, patch later." For those of you who don't know what this is, it's the new thinking of publishers to release a game, whether it be finished or not, to meet a certain criteria; such as financial status, to keep with a schedule wholly different from the developers, or just sheer plain impatience. Afterwards, they have the developers come up with a patch or upgrade to fix/add to the game. Consumers then have to scan the Internet or go to the official site to download the patch and install it. Most of the time the developers, the people who code, form, and flesh out the game, are powerle to stop this. Unfortunately, this philosophy isn't the only thing wrong with this busine . Here in this article, I'm going to go deeper into enemy territory to bring up something else that hasn't been dug into very much. I'm going to show you another area that's making the PC gaming world more frustrated by the second. It's called QA, which is short for Quality A urance. Before a game is shipped, it has to go through a QA proce , normally provided by the publisher. The QA team is supposed to have a high amount of resources at their disposal in order to track down bugs and help the developers squash them. This includes using multiple setups, i.e. different motherboards, video cards, sound cards, drivers, etc. More often then not, the QA doesn't do a thorough job. Why? Who knows. Perhaps they're too excited, in that they get to play an unreleased game. Or they don't have the skill, or motivation. It could be a ton of reasons. Blijkbaar is er maar een man die hier niet in gelooft, namelijk John Romero