Bug Fix Block

Four scheduled hours of senior engineering time aimed at your bug backlog. You tell us which defects hurt most; we work down that list in your order and ship what we can finish, with a regression test for each fix so the same bug cannot come back unnoticed. What you are buying is four hours of attention from someone who has done this before — not a promise that any particular bug falls inside them.

What you get

• Four scheduled engineering hours, worked in the priority order you set
• A regression test written for every fix that ships, so the bug stays fixed
• Each fix delivered as a reviewable change, with a note on the cause and not only the repair
• A written account at the end: what was fixed, what was diagnosed but not finished, and what we would do next

What this does not cover

• A promise that a named bug will be fixed. Four hours is four hours — some defects take one and some take a week. We work your order and we stop at four hours.
• Carrying on past the block. If a fix needs a fifth hour we stop, write up exactly where we got to, and you decide whether to buy another block. We do not keep working and invoice you for it afterward.
• Bugs we cannot reproduce. Reproducing a defect from a vague report consumes block time whether or not it succeeds, so the more precisely you can describe what you saw, the more of the four hours goes on the fix itself.
• Features, redesigns and changes of behavior. A fix makes the application do what it was meant to do; changing what it is meant to do is a Web Application Build Sprint.
• Shipping the fixes outside business hours, which is a Managed Deployment Window.

Who it fits

An application with a known list of defects and nobody left to work through it. If those defects are all symptoms of dependencies years out of date, a $60 Dependency Patch Run may clear them for a fraction of this; and if you do not yet know where the problem is, a $180 Code Review Session is the cheaper way to find out before you buy hours to spend on it.