Technical audits and advice
Some of the most useful work we do produces no code at all. A decision made carefully before a project starts is worth more than months of building, and an honest read on what you already have is worth more than a proposal to replace it.
What this covers
Technical audits
An honest read on what you have: what is sound, what is a risk, and what it would take to settle it.
Code review
A second pair of eyes on work built elsewhere, written down rather than delivered as an opinion.
Requirements and specification
Turning what you want into something that can be estimated, built and then checked against.
Training and handover
Your team left able to run the thing, with documentation that matches what was actually built.
How we approach it
Look at the whole thing
Not only the code, but how it is deployed, who can change it, what happens when it breaks, and what the business needs from it next. Problems usually live in the joins.
Say what we would actually do
Written plainly, including where the answer is that what you have is fine. Advice shaped to sell the next project is not advice.
Leave you able to act on it
Findings ordered by what they cost you and what they take to fix, so it can be handed to whoever does the work, us or anyone else.
The rest of what we do
Tell us what is not working
Describe the problem rather than the solution. Working out which part of this applies is our job, not yours.
Start a project