A patch requiring this much effort can't be a good approach to developing a computer program. It gets to a point where doing it right in the first place is a more efficient process. Troubleshooting a bug can take more time than the time it would have taken to write working code in the first place. I thought the RTW v1.2 patch, which took 3 months and almost half of the whole development team and addressed over 100 problems, went beyond this point, and now the M2TW v1.2 appears to be an even bigger effort. It's not good business, and the company's credibility as a capable developer suffers.
Bookmarks