in reply to Re: Re: Re: Production Environments and "Foreign" Code
in thread Production Environments and "Foreign" Code

You do what? No, seriously. I think there's something wrong with that attitude. I'm not arguing the usefulness of evaluation of software to be used in production - by no means.

It's not always a bad approach to make. An environment with a large number of known bugs (which you can work around) can be better that an environment with unknown bugs - even if there are less of them.

The cost of staying with a known system can be larger than the cost of migrating and discovering all those new bugs.

Of course the cost of standing still increases with time as the rest of the world moves on.

  • Comment on Re^4: Production Environments and "Foreign" Code

Replies are listed 'Best First'.
Re^5: Production Environments and "Foreign" Code
by janx (Monk) on Mar 13, 2003 at 13:00 UTC
    True enough.

    I'm just in the trouble spot of turning such a legacy system into state of the art object oriented system, so that we can finally get rid of our prehistoric database layout.
    This system has been in use for over 5 years now and been maintained (or rather mutilated) by programmers with very varying degrees of sophistication.

    So I'm very aware of having to rely on existing bugs :-(