final

Author: normanlorrain

docs/posts/2026/02/10/index.md

@@ -5,11 +5,12 @@ authors:
  - norm
 ---
 
+For those new to the term, *technical debt* is similar to financial debt. A project often starts with clean architecture and the best of intentions. Over time, however, questionable decisions creep in, changes get rushed, processes are undermined, and the codebase gradually becomes harder and harder to work with. Eventually, we reach the point of asking whether a complete rewrite is needed—sort of like declaring bankruptcy.
+
+Have you encountered technical debt in your projects? How do you deal with it? How do you prevent (or at least manage) it?
 
 
-For those who are new to the term, it's similar to financial debt.  A project starts with a clean architecture and the best of intentions.  Over time, however, questionable decisions are made, changes are rushed through, process is undermined, and the codebase reaches a point where working with the code is more and more difficult.  Eventually we ask whether a complete rewrite is needed, sort of like declaring bankruptcy.
 
-Have you seen technical debt? How do you deal with it? How do you prevent it? 
 
 Everyone and anyone are welcome to [join](https://weeklydevchat.com/join/) as long as you are kind, supportive, and respectful of others. Zoom link will be posted at 12pm MDT.