Apium Hub

In Global Software Architecture Summit in Barcelona, we talked about “Legacy Code” and there were many opinions about it. I decided to do a small research to continue investigating, I read books about this topic and talked with our software development team to see what it is exactly and what are the most common and right approaches of working with Legacy Code.

I must say that while doing this research, I saw that very often programmers call “legacy code” when they join a project and they don’t like the existing codebase. But is it right to call it “legacy code”? In our opinion – not really. If you join a project and there is a 15-year-old codebase that still does what it was designed to, bug-free, nurture it, don’t rewrite it. Users don’t care about the age of the code, they care about working software.

The common problem of software

To read the full article click on the 'post' link at the top.