Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

The same bugs keep coming back after they are fixed

Short answer

Bugs return when the fix treated a symptom, the real cause was never found, or a later change undid the fix. Ask for the cause in plain words and for a check that would catch the bug again, and make sure fixes are kept in one place.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I have reported the same problem several times.
  • The bug is marked fixed, then customers see it again.
  • A fix on one screen leaves the same bug on another.
  • My developer cannot say why it happened.
  • An old bug reappeared after an update.

Why does this happen?

  1. Only the symptom was fixed

    A quick patch hides the sign of the problem, while the cause stays and shows up elsewhere.

  2. The same mistake lives in many places

    The same bad code may be copied across the system, so fixing one leaves the rest.

  3. A later change undid the fix

    Without checks, a new change can quietly bring back an old bug.

  4. The fix was made on the live server only

    A fix not saved in the code is lost on the next release.

What can I do about it today?

  1. Write each report with stepsNote what you did, what you expected and what happened, with a screenshot, so it can be reproduced.
  2. Ask for the cause in plain wordsFor each bug, ask why it happened, not only that it is fixed.
  3. Ask whether it can occur elsewhereRequest a search for the same pattern in other parts.
  4. Ask for a check against its returnRequest an automated check, or at least a manual test, that catches this bug again.
  5. Keep a list of repeated bugsTrack which ones return, with dates, so the pattern is visible.

When should I bring someone in?

  • A bug has returned three or more times.
  • Fixes keep disappearing after releases.
  • The bug involves money or customer data.

How do I handle it?

  1. Reproduce it firstI get the bug to happen reliably before changing anything.
  2. Find the causeThe root cause is identified, not just the visible symptom.
  3. Search for siblingsSimilar code elsewhere is searched and fixed in the same piece of work.
  4. Leave a check behindA check is added that fails if the bug returns.
  5. Close with a noteYou get a short note on the cause, the fix and what protects against it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is it normal for bugs to return?

Occasionally, yes. Repeated returns point to a process gap, such as missing checks or fixes made outside the code.

How do I know a fix is real?

Ask for the steps that were reproduced before and after, and a check that guards against it.

Should I report it again?

Yes, with the original report referenced and the date it came back, so the pattern is clear.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.