Add daily email for 2025-03-22
Legacy code is anything older than...
This commit is contained in:
parent
1bc6dd2f9f
commit
852d910e6a
1 changed files with 28 additions and 0 deletions
28
source/_daily_emails/2025-03-22.md
Normal file
28
source/_daily_emails/2025-03-22.md
Normal file
|
@ -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?
|
Loading…
Add table
Add a link
Reference in a new issue