27 lines
708 B
Markdown
27 lines
708 B
Markdown
|
---
|
||
|
|
title: Refactor, remove or replace
|
||
|
|
date: 2025-01-09
|
||
|
|
permalink: daily/2025/01/09/rrr
|
||
|
|
tags:
|
||
|
|
- software-development
|
||
|
|
cta: ~
|
||
|
|
snippet: |
|
||
|
|
There are three things you can do with legacy code. Refactor it, remove it or replace it.
|
||
|
|
---
|
||
|
|
|
||
|
|
There are three things you can do with legacy code.
|
||
|
|
|
||
|
|
Refactor it, remove it or replace it.
|
||
|
|
|
||
|
|
You can refactor it to make it easier to maintain and change in the future.
|
||
|
|
|
||
|
|
If it's not needed, you can remove it.
|
||
|
|
|
||
|
|
If it's not used, there's no need to keep it.
|
||
|
|
|
||
|
|
Or you can replace it with something else.
|
||
|
|
|
||
|
|
There isn't one right answer and the correct approach will depend on the situation and objective.
|
||
|
|
|
||
|
|
In a future email, I'll give some examples of how I refactor legacy code.
|