#softwaredevelopment
Legacy code base is an existing code base that has been written in the past by software Engineers(dev) and is still being used today. When asked to work on a legacy code base you are expected to follow the pattern, structure and legacy of the person (dev) who wrote the code or set down the structure.
As a software Engineer(dev) before working on a legacy code base, ensure you request for documentation, or go through the RADME.md file. If possible request for time to go through the legacy code base. Ensure you understand the user flow and the workflow the legacy code base was written for.
Here are some of the tips you can follow.
Go through the file and check how they are related and link to each other.
Understand the structure and pattern of the code, You can innovate and work things out your way after comprehending the code base.
Ensure you stick to the technology stack being used, there are some you can learn on the job. If you feel that you want a change you can communicate it with the team and agree.
In some cases you might be allowed to do things in your own way or the pattern you write code which is rear [this often happens when the dev who wrote the code or set down the structure and pattern is not available]
In all, never criticize another person’s code base [it doesn't provide solutions], rather improve it with time, apply the DRY [Do not repeat yourself] Principle , optimize it and make it more scalable.
Ensure you do test the code know what is working, and also know what you want to work on and how they are related to other files.
How did you approach a legacy code base, share your tips below at the comment section let us learn from each other.
Follow me for more programming Tips
Top comments (0)