The 3 Types of Tech Debt Nobody Talks About Everyone writes about code debt. Here are the three types I see killing teams every day — and none of them are about the code itself. 1. Knowledge Debt This is the most expensive debt and the least discussed. It's when critical knowledge exists in exactly one person's head. You know the feeling. The deployment pipeline breaks, and only Sarah knows how to fix it. The API auth flow is undocumented, and Dave figured it out six months ago. The why behind a critical architecture decision is lost because the person who made it left. Knowledge debt compounds faster than code debt. Every time you onboard someone without documentation, you're adding to the principal. Every time you say "I'll document that later," you're deferring the payment. The fix: Write down decisions within 24 hours. Not documentation — just notes. A README explaining why you chose this approach. A comment explaining the bug you spent 3 hours debugging.…