diff --git a/docs/posts/2026/02/10/2026-02-10_desk.jpg b/docs/posts/2026/02/10/2026-02-10_desk.jpg
new file mode 100644
index 0000000..54a54d3
Binary files /dev/null and b/docs/posts/2026/02/10/2026-02-10_desk.jpg differ
diff --git a/docs/posts/2026/02/10/index.md b/docs/posts/2026/02/10/index.md
new file mode 100644
index 0000000..4097cef
--- /dev/null
+++ b/docs/posts/2026/02/10/index.md
@@ -0,0 +1,17 @@
+---
+title: "Technical Debt"
+date: 2026-02-10
+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?
+
+
+
+
+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.
+
+![messy desk](2026-02-10_desk.jpg)