ZOOMIE1980 -> RE: Quick update on development progress. (6/4/2004 7:49:01 AM)
|
quote:
ORIGINAL: Mr.Frag quote:
Your attitude in this matter is refreshingly old fashioned..., pride in your product. As I said in the Dev forum a long time back when the word "patch" came up ... "that is demoralizing, it means we failed as a team." It is really a pleasure working with 2by3. Even when they say they can't get something fixed they go off and fix it anyways. Just in the last week when we were all set for gold, Mike came along and completely gutted the TF routines and redid them from scratch. It caused a couple of major bugs and shook things up, but the end result is the odds on anything going wrong in "your" game is greatly reduced because it was done. I was scratching my head wondering how insane these guys were to make such a large change at this late state, but it just shows how committed they are to getting it right no matter what. While you might not be super happy because your favorite "XYZ" is not in the database, you will not be screaming because the game crashes on you every 15 minutes of order entry. This game can take you working for 24 hours entering in orders. It is *that* stable. "XYZ" can be dealt with in the editor, crashes can not. Wow. Talk about different worlds we live in! I guess in the gaming world, having a game that does not generate and access violation or divide by zero exception is the sign of a "stable" bug-free softwary system. In our industry, and our firm, we haven't had a half dozen hard "traps" in deliverable code in over 20 years. Bugs are almost always errors in processing logic or lack of conformaty to contracted external specification. A stable system is a system that performs a billion financial settlement transactions over six months without a single processing error and one microsecond of down time. Just a difference in cultures, I suppose. But then again, when you code in straight 'C', pass old-style pointers around, "roll your own library code vs using mature, stable, external toolkits, and use fixed data arrays, access violations are par for the course, I guess.
|
|
|
|