Re: Akabur Games
Of course every task takes some amount of time. We can also look at the results and the time taken and decide the two don't match up well. To rephrase something I've said before, if he releases it in March of next year, and there are 3 new CGs, 4 new quests, and the wardrobe feature, all of which takes under 2 hours to play if you read slowly, I think you have to question your support of that.
There are really four main options that I see: 1) He'll be some level of successful, everything he says is true, and the game will be decent to amazing. 2) He's milking it deliberately for a pay-day. 3) He's just plugging along whenever he feels like working and collecting a paycheck regardless. 4) He's actually working very hard, but not really up to the tasks he set (programming is a particular Achilles heel). Options 2 and 3 will be indistinguishable to us, unless he tips his hand somehow, and 4 could be in that mix as well unless he leaves thousands of lines of copied & pasted crap in the code with slight changes that were obviously done by a frantic hand. Hell, it could be a mix of the last 3 or even all of them over the course of many months. The end result will tell, and if it seems likely that the bad options dominated development, there's no reason to support him any more, even if his job actually is "just so damn difficult".
Of course every task takes some amount of time. We can also look at the results and the time taken and decide the two don't match up well. To rephrase something I've said before, if he releases it in March of next year, and there are 3 new CGs, 4 new quests, and the wardrobe feature, all of which takes under 2 hours to play if you read slowly, I think you have to question your support of that.
There are really four main options that I see: 1) He'll be some level of successful, everything he says is true, and the game will be decent to amazing. 2) He's milking it deliberately for a pay-day. 3) He's just plugging along whenever he feels like working and collecting a paycheck regardless. 4) He's actually working very hard, but not really up to the tasks he set (programming is a particular Achilles heel). Options 2 and 3 will be indistinguishable to us, unless he tips his hand somehow, and 4 could be in that mix as well unless he leaves thousands of lines of copied & pasted crap in the code with slight changes that were obviously done by a frantic hand. Hell, it could be a mix of the last 3 or even all of them over the course of many months. The end result will tell, and if it seems likely that the bad options dominated development, there's no reason to support him any more, even if his job actually is "just so damn difficult".
