Step 1
Send me the bug
Symptoms, environment, how often it bites, and what has already been tried. Screenshots, logs, and failed theories all help.
Fixed-scope offer · Debugging
Stuck on a Difficult Bug? I’ll Find the Root Cause
Some bugs eat weeks: they vanish under a debugger, appear only in production, or live across three systems at once. Send me the bug — I investigate it with a fixed scope, and you get the root cause, a fix, and a regression test. Not a shrug.
When to bring me in
The bugs this exists for.
- The bug does not reproduce consistently
- Race conditions
- State management issues
- Memory leaks
- Slow React rendering
- Broken authentication flows
- API integration issues
- Bugs that only appear in production
- Streaming and real-time problems
- Regressions after a deployment
- Flaky frontend behavior
Deliverables
What you receive.
- Reliable reproduction steps
- Root-cause analysis: what actually happens, and why
- A technical explanation your team keeps learning from
- A fix or a patch
- A regression test so it cannot come back silently
- A recommendation to prevent the same class of bug
Process
How it works.
Step 2
Scope and access
A short call to agree the scope, then read access to the code and logs — under NDA if needed.
Step 3
Investigation, fix, writeup
I isolate the root cause, ship the fix or patch with a regression test, and explain it so the team recognizes the pattern next time.
FAQ
Common questions.
What if you can’t find the root cause?
Honesty is part of the deal: if I cannot reproduce or isolate the bug within the agreed scope, I say so — and you still get a documented investigation, the hypotheses eliminated, and a concrete plan for what to instrument next. You will not get a hand-wavy guess dressed up as a diagnosis.
Our code is confidential. How does access work?
Read access under NDA is standard. If full repository access is off the table, we can scope the investigation around a reduced reproduction, logs, and pairing sessions with one of your engineers.
Do you fix it, or just explain it?
Both, whenever the fix fits the agreed scope — the deliverable includes a fix or patch plus a regression test. For root causes that demand a larger change, you get the precise diagnosis and a realistic plan for the fix.
Evidence
Related production work.
Writer
Building the workflow layer that makes enterprise AI agents usable
AI agents demo well and fail quietly. At Writer I build the layer that makes them dependable: workflow structure, grounded knowledge, enterprise identity, and the unhappy paths.
Cato Networks
Hardening a network-security admin platform while it kept shipping
Security consoles can’t have bad days. At Cato Networks I modernized legacy admin infrastructure and shipped new mission-critical screens — without pausing the release train.
Tell me what is blocked, underperforming, or difficult to ship.
I will tell you whether I can help — and what the smallest useful next step would be. If I’m not the right person, I’ll say so.