I am hung up on the definition of legacy system and how IT folks have started using them in general. Now a days, every Tom, Dick & Harry have started using this term and in some really vague and wierd sense. So, what really comprises of legacy system? I have seen people started using this term so loosely that even the current system sometimes gets refererd as 'legacy'. And IT is really quick to act on it. Add more resource and start writing code in a better technology (so they think). I guess, referring system as legacy is one way of telling that a system is old. But old is not bad is it? As long as it meets the business requirements and has the right architecture old is really not bad. But as  computer world that we are all in, the latest architecture defined today is going to be obsolete tomorrow which will make applications built on MVC, SOA, SilverLight, ADO.net data services obsolete. Imagine that...

Even wikipedia defined legacy system as "System those are potentially problematic". Is that really true? An introspection is needed. I think!