What is technical debt?

Technical debt is the accumulated cost of shortcuts, outdated code and quick fixes in a website or app, which makes future changes slower, riskier and more expensive.

Curious how your site handles technical debt?

Send me the address. I’ll look under the hood and tell you plainly what I find, free.

No newsletter. Just what you asked for, from me. Privacy

In plain English

Like financial debt, technical debt isn’t always bad. A quick fix can be the right call to meet a deadline. But it accrues interest: each shortcut makes the next change harder, until simple updates take days.

Common sources include outdated plugins, layered theme overrides, abandoned code and features bolted on by different developers over the years.

Why it matters for a small business

On a small business site, technical debt shows up as “we can’t change that without breaking something,” slowing pages and security warnings. Eventually a rebuild becomes cheaper than another patch.

An example

A Calgary dental clinic’s site has been edited by four developers over many years. Changing the phone number in the header requires editing three files, because each developer added their own version. A small cleanup consolidates them, and future updates become routine again.

Common mistakes

Where I see technical debt go wrong most often.

  1. Ignoring small issues until they compound into a site nobody wants to touch.

  2. Asking each new developer for quick fixes without anyone owning the overall code health.

  3. Rebuilding everything when a targeted cleanup would solve the real problem.

FAQ

Technical debt, answered

  1. If small changes take far longer than expected, updates often break things, or developers hesitate to touch parts of the site, it likely does.

  2. Not entirely, but regular maintenance, clean code and a single owner of the codebase keep it manageable.

Keep reading

Let’s begin

Let’s build something you’re proud to share.

Let’s Talk