From 61faa23c8fca4dca92ba0f8d6725eab68d565ead Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Thu, 21 Mar 2024 00:29:44 +0000 Subject: [PATCH] Add daily email for 2024-03-20 What is technical debt? --- source/_daily_emails/2024-03-20.md | 37 ++++++++++++++++++++++++++++++ 1 file changed, 37 insertions(+) create mode 100644 source/_daily_emails/2024-03-20.md diff --git a/source/_daily_emails/2024-03-20.md b/source/_daily_emails/2024-03-20.md new file mode 100644 index 000000000..ade534911 --- /dev/null +++ b/source/_daily_emails/2024-03-20.md @@ -0,0 +1,37 @@ +--- +title: What is technical debt? +date: 2024-03-20 +permalink: archive/2024/03/20/what-is-technical-debt +tags: + - software-development + - clean-code +cta: ~ +snippet: | + How do _you_ define technical debt? I can think of several potential definitions. +--- + +How do you define legacy code? + +Is it code written by previous Developers who worked on the codebase? + +Is it code you wrote last week or last month? + +Is it code for features everyone no longer uses? + +Is it the "old" part of the application that no one wants to work on? + +It is any code that's not nice to work on or difficult to change? + +Is it code written with different conventions to your current ones or in a different style? + +Is it any code that doesn't have automated tests or wasn't written with test-driven development? + +Is it code built with outdated tooling or frameworks (like CSS libraries) that were popular then but have since been replaced by something newer? + +## Here's the thing + +These are just some of the potential definitions I can think of. + +The term "legacy code" and others, such as "technical debt", often mean different things. + +What's your definition? Reply and let me know.