3 ms·
> Microsoft gave us a choice: either pay a ton of money to re-certify the game and issue a new patch (which for all we know could introduce new issues, for whic
by justin66 14y ago
> Microsoft gave us a choice: either pay a ton of money to re-certify the game and issue a new patch (which for all we know could introduce new issues, for which we’d need yet another costly patch), or simply put the patch back online. They looked into it, and the issue happens so rarely that they still consider the patch to be “good enough”.
To someone with no background on this at all, this is just painful to read. That parenthetical bespeaks a lazy attitude towards engineering. "Why fix it when we might just break it again? It's not like we're actually good enough at this to have confidence in our work!"
- yen223 14y agoTheir cost/risk analysis plays out. If the new patch somehow introduced a new bug, it's going to cost them yet another large amount of money to fix it. And if you say "well just make sure the new patch doesn't break anything, duh!", then you clearly haven't been in software engineering long enough.
- justin66 14y agoI certainly believe it's possible to write and test a patch for a single, well-understood bug and deploy it with a reasonably high degree of confidence that it will not introduce any new issues.