From fd7d951809e9d33ac3d4056c1d9194c0e5160a81 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Mon, 7 Oct 2024 23:32:00 +0100 Subject: [PATCH] Add link --- source/_daily_emails/2024-10-02.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/_daily_emails/2024-10-02.md b/source/_daily_emails/2024-10-02.md index b6e18d71..a10f8320 100644 --- a/source/_daily_emails/2024-10-02.md +++ b/source/_daily_emails/2024-10-02.md @@ -9,7 +9,7 @@ snippet: | Taking on technical debt isn't always bad. --- -Technical debt is usually referred to negatively, but technical debt isn't always bad. +[Technical debt is usually referred to negatively][0], but technical debt isn't always bad. The key thing is to know when and why you're taking on technical debt and when it will be addressed. @@ -22,3 +22,5 @@ For the initial version, that approach was good enough and meant we could move f The client and I decided to take on this technical debit in advance so we could release it sooner, and we knew when and how we were going to address it and pay it back. This was a good situation, not a bad one. + +[0]: {{site.url}}/daily/2024/10/01/not-all-legacy-code-is-technical-debt