[0x0000000]

You can't just be in your codebase and start doin' technical debt like that. 1a. Technical debt is when you... 1b. Okay, wait. Technical debt is when you write code but, like, the kind of code that you know Future You is gonna hate. 1c. Let me try this again.

1c-a. It's when you're coding and you think, "I'll fix this later," but then later turns into never. And now there’s spaghetti code in a project that was supposed to be a sleek pipeline.

1c-b. Like, imagine you're about to refactor something, but you go, "You know what? The deadline's tight, so I’m just gonna... not." That’s technical debt.

1c-b(1). If you're writing code and you think, "Wow, I hope no one sees this commit message," congratulations, you’ve accrued technical debt.

1c-b(2). It’s like leaving a TODO comment, except the TODO becomes, “Oops, it’s been in production for three years.”

1c-b(2)-a. You can write a clever workaround here, but the workaround has to work around the workaround of the workaround from three sprints ago.

1c-b(2)-b. Also, don't forget to include an inline comment that says, "This should be fine for now," which is developer code for “This is the next intern’s problem.”

1c-b(2)-b(i). Fun fact: the "for now" phase lasts forever, and the fix will never be fine.

1c-b(3). Seriously though. Technical debt is when your code does the thing but not in the way anyone would ever want it to. And if your app suddenly catches fire during peak traffic, that’s just the interest being collected.

    Do not do technical debt, please.

[cyanydeez]

Technical debt can also be aa simple as having a python 2 project in 2024. You can do everything right but the environment changes.