Code reviews are one of the best things you can do to improve code quality, but the process isn't a silver bullet. These are my observations on what works and what doesn't work when it comes to implementing code reviews.
This was exactly my reaction when I saw the title of the article. Regarding development of the first title, he said, It was a tremendous learning experience for us. So then they decided to throw away all the people who learnt from those experiences. I wish everyone from Kaos all ...
World in Conflict was along similar lines to Ground Control, and was similarly awesome, but for some reason didn't really catch on. It's a shame that the console version was canned because I thought it was an ideal fit for a console RTS.
I second the notion of doing indie projects until you get a paying job. It doesn't really seem like a risk if you aren't getting paid anyway, and the experience should help you find that job. Or maybe your project will be a hit and you won't even need someone ...
I see this game on XBLIG all the time, but I never bothered to take a closer look at it. Based on this review though I'm thinking of picking it up, or at least trying the demo.
