Knowledgebase

Deciding When to Take on Debt Print

  • softwareengineering, software, hacked, domainrenewal, security, billing, guide, howto
  • 0

Deliberate compromise.

WHEN IT IS DEFENSIBLE

A genuine deadline where being late costs more Validating whether something is wanted before investing An experiment that may be discarded A temporary measure with a defined end

WHAT MAKES IT DEFENSIBLE

Being deliberate, recorded, and planned for repayment.

WHAT MAKES IT RECKLESS

Being unrecorded Having no plan Becoming permanent by default

WHAT TO RECORD WHEN TAKING IT ON

What was compromised Why What it will cost When it will be addressed

WHERE TO RECORD IT

In the code, and in the debt register.

WHY IN THE CODE

So whoever encounters it understands it was deliberate.

WHAT TO AVOID

Temporary solutions with no expiry.

WHY

Nothing is as permanent as a temporary solution.

WHAT TO NEVER COMPROMISE

Security Data integrity Anything affecting money

WHY

Those are not debt. They are defects.

WHAT TO ASK

If we never address this, what happens?


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot