Practice
Our standards exist for one outcome: your team can maintain what we build after we leave. That means typed code, tests on the logic that matters, documented decisions, and a handover that is planned rather than improvised.
Context
Standards decide whether your team can maintain what we build after we leave. That is the only measure of a handover that matters.
Choices
Every choice below has a reason attached. A stack without reasons is a logo wall.
Boundaries
Recommending something everywhere is the same as having no opinion. These are the cases where we would tell you to do something else.
Our standards exist for one outcome: your team can maintain what we build after we leave. That means typed code, tests on the logic that matters, documented decisions, and a handover that is planned rather than improvised.
Standards decide whether your team can maintain what we build after we leave. That is the only measure of a handover that matters.
Throwaway prototypes built to be discarded: full rigour there is waste; and Experiments where the goal is learning, not shipping
Errors surface at build time rather than in production.
No single-author code paths in anything we hand over.
Both regress silently unless a build fails. Treating them as review comments means they degrade over time.
The reasoning behind a choice is worth more to the next engineer than the choice itself.
Documentation, walkthroughs and a support window. IP is yours from day one.
Connected
Bring the existing system and the constraints around it. We will tell you where this fits, where it would be the wrong tool, and what we would leave exactly as it is.
