---
title: "Comment by thepurplecoder on \"8 Things I've Learned Working in a Legacy Codebase\" | Hashnode"
description: "Great article Abbey Perini . Agree with all the points. Do you have any advice for people who refactors legacy codebase? I generally find this hard especially i"
url: "https://hashnode.com/posts/8-things-ive-learned-working-in-a-legacy-codebase/614388912d0e2479882a2d4b/comment/6144c6cf2d0e2479882a4e61"
---

[Discussion](https://hashnode.com/posts/8-things-ive-learned-working-in-a-legacy-codebase/614388912d0e2479882a2d4b)

Comment [8 Things I've Learned Working in a Legacy Codebase](https://hashnode.com/posts/8-things-ive-learned-working-in-a-legacy-codebase/614388912d0e2479882a2d4b)

[thepurplecoder](https://hashnode.com/@thepurplecoder)

[Sep 17, 2021](https://hashnode.com/posts/8-things-ive-learned-working-in-a-legacy-codebase/614388912d0e2479882a2d4b/comment/6144c6cf2d0e2479882a4e61)

Great article [Abbey Perini](https://hashnode.com/@abbeyperini). Agree with all the points.

Do you have any advice for people who refactors legacy codebase? I generally find this hard especially if there is no proper documentation for the codebase.

[Abbey Perini](https://hashnode.com/@abbeyperini)

[Sep 17, 2021](https://hashnode.com/posts/8-things-ive-learned-working-in-a-legacy-codebase/614388912d0e2479882a2d4b/comment/6144c6cf2d0e2479882a4e61#reply-6144d0f4dbe60379639b2c50)

For testing and bugs - A lot of notes! I take notes every day to help me remember where I was when I log back in the next day or after the weekend or PTO. I document every change I made in the ticket when I finish it, often with file names and even lines. Leaning on a version control GUI like Sourcetree helps as well.

For writing the new code - Document exactly how what you're changing behaves before you change anything. I appreciate when QA sends me videos of bugs. It helps a lot. Make small, manageable changes and test. Repeat. Discuss with your team (especially QA - they know how to break things) and brainstorm what workflows could possibly be affected. Be prepared for unexpected consequences. I cannot praise my QA team and our automated suite of end to end testing enough.
