Skip to main content
IVAN HRYNIUK

Bug fixing

Forms that silently fail, pages that error, a layout that collapses on phones, a checkout that loses orders. The work starts with finding the actual cause rather than patching the symptom.

A good fit when

  • Your original developer is unavailable and something has broken
  • A problem has been "fixed" more than once and keeps returning
  • You need someone to work on a codebase they did not write

What is included

  • Broken forms, failed submissions and lost enquiries
  • JavaScript errors, blank pages and console noise
  • Layout and responsive problems on specific devices or browsers
  • Broken integrations, webhooks and third-party scripts
  • Deployment failures and builds that stopped working

What you receive

  • A plain-language explanation of what was actually wrong
  • The fix, deployed and verified on the live site
  • A note on anything else found along the way, with a recommendation
  • Where useful, a guard so the same failure cannot return silently

How it works

  1. Reproduce

    First the fault is reproduced reliably. A bug that cannot be reproduced cannot be confirmed fixed.

  2. Diagnose

    Logs, network traffic, error tracking and the code itself, until the cause is known rather than guessed at.

  3. Fix and verify

    The smallest safe change that resolves the cause, tested and then deployed — with a rollback path if anything unexpected appears.

Pricing

Every engagement is quoted individually after a short conversation about scope. Quotes are given in GBP and confirmed in writing before any work starts.

Have a website to build, or one that needs fixing?

Describe the problem in a couple of sentences. You will get a considered reply, not a sales sequence.