---
title: "Discussion on \"8 Things I've Learned Working in a Legacy Codebase\" | Hashnode"
description: "Discussion on \"8 Things I've Learned Working in a Legacy Codebase\". My first dev job threw me into a huge legacy codebase. My last big ticket involved getting a modern library to work within the deprecated UI framework it uses. After that journey, I wanted to share some tips I've learned along the way.\n\n(1) Learn the..."
url: "https://hashnode.com/posts/8-things-ive-learned-working-in-a-legacy-codebase/614388912d0e2479882a2d4b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [8 Things I've Learned Working in a Legacy Codebase](https://abbeyperini.hashnode.dev/8-things-ive-learned-working-in-a-legacy-codebase?utm_source=hashnode&utm_medium=feed)

My first dev job threw me into a huge legacy codebase. My last big ticket involved getting a modern library to work within the deprecated UI framework it uses. After that journey, I wanted to share some tips I've learned along the way. (1) Learn the...

Sep 16, 2021 · 4 min read · abbeyperini.hashnode.dev  
Read the article

-   [#coding](https://hashnode.com/tag/coding)
-   [#programming-tips](https://hashnode.com/tag/programming-tips)
-   [#learning](https://hashnode.com/tag/learning)
-   [#web-development](https://hashnode.com/tag/web-development)
-   [#programming](https://hashnode.com/tag/programming)

## Written by

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

@abbeyperini · Atlanta, GA

  
[View profile](https://hashnode.com/@abbeyperini)

Full-stack Web Developer

Abbey Perini is many things - a metro Atlanta native, person of many hobbies, full-stack web developer, accessibility advocate, international speaker, and technical writer with ✨over 500,000 views.✨ She's full-stack in the truest sense - give her a problem and she'll figure it out. She's happiest problem solving in the front-end, back-end, and all the APIs and microservices in between. Passionate about accessibility, she's worked in Vue, React, and even AngularJS (2013). She's spent her development career rectifying tech debt in existing codebases.

## Responses 7

Markdown supported · ⌘↵ to post

[Nicholas Stanley](https://hashnode.com/@NicholasStanley)

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

wow

[Jide Abdul-Qudus](https://hashnode.com/@jideabdqudus)

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

Nice article [Abbey Perini](https://hashnode.com/@abbeyperini) I've had a similar path in working with legacy codebase and all of the points you listed were helpful.

[Mausam Singh](https://hashnode.com/@mausamsingh470)

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

I was **amazed** after reading this "It worked **65M** years, No one knows how and no one knows why🤔"

[Ajith jojo](https://hashnode.com/@codeconia)

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

Nice article

[Shad Mirza](https://hashnode.com/@iamshadmirza)

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

Very helpful.

[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.
