Service
Bug Fixing& Support
Most of what I am sent is code somebody else wrote. I start by reading the model and the access rules before changing anything — a fix that quietly breaks a workflow someone depended on is not a fix.
4 in scope
You probably need this if
Any of these sound familiar.
A screen that has become too slow to use
A regression that appeared after an upgrade
An error nobody can reproduce reliably
A module whose original developer is gone
In scope
What the work actually covers.
01Reproducing the fault on a copy of the real database
02Root-cause fixes rather than a guard around the symptom
03Query profiling and ORM tuning on the slow views
04Ongoing support arrangements, monthly or by the hour
What you end up with
The fault gone, the cause written down, and a note on what to watch if it starts again.
Also available
Next step
Start a projectTell me what the process does today and what it should do instead. I will come back with a scope.