From 852d910e6af29ec01a643a8af4d9dad13c7a3092 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Wed, 26 Mar 2025 23:53:34 +0000 Subject: [PATCH] Add daily email for 2025-03-22 Legacy code is anything older than... --- source/_daily_emails/2025-03-22.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 source/_daily_emails/2025-03-22.md diff --git a/source/_daily_emails/2025-03-22.md b/source/_daily_emails/2025-03-22.md new file mode 100644 index 000000000..2a6020efe --- /dev/null +++ b/source/_daily_emails/2025-03-22.md @@ -0,0 +1,28 @@ +--- +title: Legacy code is anything older than... +date: 2025-03-22 +permalink: daily/2025/03/22/legacy +tags: + - software-development +cta: ~ +snippet: | + How old does code need to be before it's considered legacy? +--- + +How do you define legacy code? + +Code that was written by someone else? + +Code that doesn't have tests? + +Any code that has been released to production? + +Code that's more than a day old? + +In a talk I recently watched, the speaker suggested that any code written more than thirty minutes ago is legacy code. + +Once you've written some code and left it for half an hour, you need to re-read it to remember and re-learn what the code does and decide how you want to implement your next requirement. + +This is the same approach for code that was written longer ago or written by someone else. + +What do you think?