Christian Seberino wrote:
But why is it so important to have the new code be at parity with old spaghetti code at all times? What's wrong with it being deficient for a while until it gets banged into shape?
Nothing necessarily wrong with that. You can let the regression tests fail for a while if you want. But eventually you will want to come back and fix that stuff and how will you ever remember what it was that needed fixing? It is important that the final product be at parity with the old code in a case where you are releasing a new version of software which is just a minor revision number different and therefore should be completely compatible with the previous version so nobody's stuff breaks, just for one example.
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
