It worked, then it broke
It did its job, then stopped or went wrong: a display fault, a form that no longer submits, a report that will not run, a figure that has been quietly off.
Application fixes & debugging · PHP, Perl & Python
The job nobody will quote, or quotes to be turned down.
Something is broken, wrong, or doing what it was told rather than what was meant. A display fault, a calculation that has been quietly wrong, a form that stopped submitting, a report that will not run. Or most of it is fine, and a few small things are wrong or need to change.
$20 an hour. Five hour minimum. PHP, Perl or Python, scoped against what it does now, so the work does not become a project. Finding a bug and fixing it are not always the same job: hire either one, or both.
For new clients: one free review covering one application on one server or hosting instance. Review terms →
Debugging and bug tracking are separate from fixing.
A different export, a hook, a rule that needs to change.
Hours agreed against what it does now, before work begins.
What it looks like
You do not need to know why. Describe what you see and what you expected to see.
It did its job, then stopped or went wrong: a display fault, a form that no longer submits, a report that will not run, a figure that has been quietly off.
It has always done what it was told rather than what was meant, or never did the job it was built for.
Most of it is OK. A small thing here and there is wrong, or does not suit how the business works now.
When most of the application is fine and one thing needs to change, that is a fix, not a project.
Describe · reproduce · trace · report · fix
Stop after the report if all you need is the cause, or carry on to the fix. Either way the hours are agreed against what the application does now, before work begins.
01
What you expected, what happens instead, and where. Examples and screenshots help.
02
We reproduce the fault on your system. Intermittent bugs are tracked until they can be made to happen.
03
Debugging: follow the fault to its cause in the code path, the input, the data or a setting.
04
What was found, where, how to reproduce it, and the options. You can stop here.
05
If you want it: the smallest change that corrects the behavior, no rewrite. You confirm it against the case you reported.
Depends on the size of the code base. A small change may not need an audit; a larger code base does. Stack dependencies audit →
Technical
Start with what is broken
Tell us what is broken and what it should do. Ask for the cause, the fix, or both. We scope it against what it does now and agree the hours before any work begins. Five hours at $20 makes the smallest job $100.
For new clients: one free review covering one application on one server or hosting instance. Review terms →