See, I disagree.
Bugs will exist - it's the nature of software development. Yes, we can look back and say "this scenario is so obvious, how did no one think to check this?" but ultimately, it happens.
The difference is response times. Within two weeks, every major bug found has been identified and fixed. Someone picking up the game today, still on sale at full price, will have a polished, smooth experience. Compare that to other games, who close to six months later still have long-standing known bugs that show no end in sight.
I don't mind the bugs being in the game... as long as the company can fix them quickly and effectively.
Not at that critical level. Jimmy, the user testcase for double clicking shouldn't have even existed if this thing was tested. I like the game but from a user perspective how many times is someone going to double click? I would have understood if it is a build or code revision issue but not something constantly in the original product. This is why people do TDD http://en.wikipedia....ven_development .
I would like to interview an obsidian developer and just find out their process. Response time is a good point but implementation should also be looked at under a microscope. What is it about their process that results in these issues? Are they following good coding standards? How much of their time is spent testing? How are they testing their code? To me it looks like a combination of not properly managing time + the idea of "churn out code and we will fix it later"





Guest_TrillClinton_*
Retour en haut







