If you are maintaining a legacy codebase, it probably means you or someone else did something right. Perhaps there are still people using it, but how hard is it going to be to support it? How long will it be used for? A better question is - how do we write code that becomes good legacy code one day? There are many articles and talks about how to write a maintainable codebase which I don't want to repeat; however, as someone who worked on a 15-year-old application, I have come up with a wish list. This list includes things that could have made my life easier or things that I was thankful for and helped me a lot. In this talk, I will go through some of the issues I faced when maintaining legacy code. Issues like decoupling, dependence on the underlying hosting platform, testing, third party integrations, and more. The goal of this wish list is to help you write code that can be used for longer. Check out more of our featured speakers and talks at https://www.ndcconferences.com https://ndcmelbourne.com/
Get notified about new features and conference additions.