Add link
This commit is contained in:
parent
aba55d76ba
commit
fd7d951809
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue