From 4693e26daf0a0264aafb55e3b0371ed386875435 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Mon, 13 Jan 2025 22:03:04 +0000 Subject: [PATCH] Add daily email for 2025-01-09 Refactor, remove or replace --- source/_daily_emails/2025-01-09.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 source/_daily_emails/2025-01-09.md diff --git a/source/_daily_emails/2025-01-09.md b/source/_daily_emails/2025-01-09.md new file mode 100644 index 000000000..fe498c319 --- /dev/null +++ b/source/_daily_emails/2025-01-09.md @@ -0,0 +1,26 @@ +--- +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.