Andrew Lentvorski wrote: > 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? > > Because you have no proof it will ever "get banged into shape". > > Furthermore, since you are unlikely to have unit tests on the old code > (unit tested code rarely gets called spaghetti), you have no knowledge > of when it actually does get banged into shape.
I'd like to echo that last point. Q: How do you know when the code is done? A: When all the required tests have been written and they all pass. There's always more to say, but that's a nice reference point. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
