Service · Keep it running
Software bug fixing and debugging, even if someone else built it
Something's broken, slow or doing odd things. We find out why and fix it properly, even if someone else built it.
Sound familiar?
The problem
It worked last month. Now orders go missing, the app crashes, and the developer who built it isn't answering.
What we do
- Reproduce the problem so we know exactly what's going wrong.
- Read the code and the logs to find the cause, not just the symptom.
- Fix it, and add a test so the same bug can't quietly come back.
- Tell you in plain words what happened and what we changed.
How it works
Fixing and debugging, in one picture
- 01Make it happen again
- 02Find the real cause
- 03Fix it properly
- 04Test the fix
- 05Write it up
What you get
Things you can hold us to
- 01The fix, tested and deployed
- 02A short report on the cause and the change
- 03Tests that guard against the bug returning
- 04Notes on anything else risky we spotted on the way
From the notebook
Guides worth reading
- Software projectsInheriting software from a developer who left: a rescue checklistYour developer has gone and the software is yours. A step by step checklist to get access, understand what you have and keep it running.Read the guide
- Software projectsHow to choose a software development company in Nigeria: 12 questions to askTwelve questions to ask any software development company in Nigeria before you sign: how they work, who owns the code, testing, support, pricing changes and more.Read the guide