3 ms·

I don't think something created in 2008 can be considered a legacy system

• m4tthumphrey 6y ago
  It definitely can. We have a project on our books that was started in 2010. It was built using Flex (Flash) so was already legacy before one LOC was written.
• LandR 6y ago
  I'm working on code that was built three years ago, It would be considered it legacy code as soon as it was deployed the quality is so low.
• wirthjason 6y ago
  The date doesn’t matter so much (to me at least). Legacy means lack of tests and the inflexibility to change the system. Working on these systems it’s easy to have a part of the app become obsolete in 2-3 years because it’s written by one someone who doesn’t really care about technology and they want to “deliver for the business” so they crank out some shitty code with no tests, documentation, or design of any kind (eg encapsulation). The business rules are complex and not explained or understood. Then the main developer leaves and all that knowledge vanishes out the door.
  • StavrosK 6y ago
    I've seen systems that were legacy before they were written.
• p_l 6y ago
  I'm dealing currently with legacy code that is less than 1 year old. The discussion is already at the level of "we would do the rewrite from zero if not for timeline issues".