25

Amazing how people misuse the term technical debt.

A bug is a flaw in your design/development.

Tech debt is a conscious decision/tradeoff, which is often tracked and removed as the product matures.

The difference is subtle. Avoid this mix up at least in written communication.

Comments
  • 4
    You sure it isn't the catch all to dump shit you should've done but need to drop to cut corners to meet the arbitrary cyclical sprint deadline lest management cast its baleful eye on the poor codemonkey wageslaves?
  • 1
    Indeed, a product of only a few months old does not have a technical debt (unless absolutely no structure is applied anywhere in the process).
  • 4
    If the decision is to ignore the bug, then it becomes technical debt.
  • 0
    @sjwsjwsjw Yup! Do you read minds ? 😁
  • 0
    @matste On Realistic grounds, yes. Ideally it shouldn't be though
  • 0
    @Codex404 Even if it a pending unit test or integration test, it qualifies as a tech debt.

    Usually these are the things that take a hit when the deadlines are merciless. Depending on the team culture, these debts would be cleared(or not).
  • 2
    Idk, I've seen plenty of unconsciously generated technical debt... :/ It haunts me.
  • 1
    @ihatecomputers "unconsciously generated technical debt" is ambiguous and provides people with an opportunity to hide things under the carpet!

    Technically, this phenomenon exists. But acknowledging it, just creates a chances to the opportunists!
  • 2
    I just toss out that word to my boss to justify why certain projects he assigned me to maintain will take longer than “2 seconds” to fix.
  • 0
    @monzrmango good strategy 😆
Add Comment