News for hackers. Stuff that matters.

A comment on How To Identify A Lame Programming Job. Parent comment

Re:How To Identify A Lame Programming Job by prodigal_erik on Friday December 04, 2009 @04:41AM (#976070)
To me "legacy" connotes flawed, not merely old. If a rewrite would end up slightly modernized but basically the same, what you have is an investment. If a rewrite would end up completely different because the old version doesn't meet the current requirements, what you have is a legacy problem.
[ Parent | on HN ]
Re:How To Identify A Lame Programming Job by access_denied on Friday December 04, 2009 @02:20PM (#976985)
You are distinguishing between "legacy" and "legacy problem" and thus rendering your own opening 'thesis as moot.
[ Parent | on HN ]
Re:How To Identify A Lame Programming Job by prodigal_erik on Saturday December 05, 2009 @02:05PM (#978428)
Sorry, what I was trying to get across is that I don't expect to hear "legacy" unless there's a problem.
[ Parent | on HN ]