How we build
The practices a cheap quote leaves out.
We are not the lowest bid, and this is where the difference goes. Most of what follows is invisible on a quote and obvious two years later, when someone else has to work on the code.
01Changes get reviewed
On any project with more than one engineer, code is read by someone else before it reaches the main branch. Review is where most of the defects a client would eventually find get caught instead.
02Version control from the first commit
Git, in a repository under your organisation, with branches per feature and a readable history. You can see what changed, when and why, without asking us.
03Automated tests on the parts that matter
Tests on business logic, integrations and anything money passes through. We do not chase a coverage percentage, because a high number on trivial code proves nothing.
04Separate staging and production
Changes are proven on a staging environment that matches production before they reach live users. Urgent fixes go through the same route, so what is running always matches what is in the repository.
05Automated build and deploy
A pipeline runs the tests and ships the release. Deploying is a routine action rather than an event someone has to be talked through over a call.
06No fragmented hours
When an engineer is assigned to your work for a block of time, that block goes to your work rather than being split across three clients in the same afternoon. People do move between projects as phases finish, and who is on yours is always visible to you.
07Written scope, written decisions
What was agreed, and what changed since, exists in writing rather than in someone's memory of a call. This is what makes a handover possible at all.
08Documentation as a deliverable
How to run it, how to deploy it, how to extend it. Written for the developer who inherits the project, which is often not us.
09Transparency by default
Ask who is on your project, what stage the work is at, or why something is taking longer than expected, and you get a straight answer rather than a managed one. Bad news reaches you while there is still time to act on it.
None of this is unusual for a good engineering team. It is unusual in a quote priced to win on number alone, because every item above costs hours that a cheaper bid has to leave out. The saving shows up later, as the rebuild.
