new things good, old things bad!

if that sounds decidedly orwellian, it is.

I'm now working with a certain team where the idea "new is good" is highly promoted. As a result, they are willing to throw away code that has been used for ages just to try to put in new stuff (without showing that the new prototype works)

unfortunately, the proposed changes have the potential to create big ripple effects - the picture i had in mind was more of a tidal wave - and that was overlooked by "oh, so? we want to fix the problem, right?"

we do want to fix the problem. but not by introducing new ones. and not before we can prove that we can fix a problem. get a working prototype that work before telling the old model to "go forth, be fruitful and multiply".

..as i seem to remember, the titanic was new when it sank..