I don't know what to tell you. I work for local government, and we do a lot of things unoptimally, but it's not difficult to maintain multiple content streams and build selectively if you've designed your application to do that.Fast Jimmy wrote...
Yes, release and development management should be able to properly identify the other modules affected, but SHOULD and DO aren't always the same. I can't even begin to count how many nights I've been up far past midnight with a production release that has now made a totally unrelated (or so many people thought) program completely unusable. After months of testing, there winds up being some small unforeseen correlation that causes the release to be pushed back and hundreds of hours testing could not catch what one code change made apparent in less than ten minutes of using.
Point being, nothing is perfectly modulized, nothing is as safe as tested content. And you can't say you've truly tested something thoroughly until its in as close to its final state as possible.
Skyrim's esm/esp/etc (et cetera, .etc isn't a file exension...) are the best example of this for gaming (which is why I used Skyrim as an example before). It is remarkably simple to develop a mod/DLC/expansion separately from the main game files.
Retour en haut
