resources

The standards we work to, published.

These are the working documents behind our engagements: how we keep a codebase verifiable, with checks nobody can skip and rules the compiler enforces. Read them, copy them, adapt them.

7
themes
33
engineering techniques
8
to do first
01 · engineering practices25 min read

Engineering practices that survive the stack

The structural habits that keep a codebase honest: checks nobody can skip, rules the compiler enforces, and state with a history. Each is a rule, the thing to build, and the mistake it replaces.

  • Verification that is structural, not voluntary
  • Rules encoded in the compiler instead of a document
  • One home for every version and constant
  • Checks that are deterministic, and proven able to fail
  • Version history for schemas and other durable state
7
themes
33
techniques
8
to do first
Read
markdown

how to use them

Useful in an afternoon.

No guide here asks you to change your stack. Each is ordered so the first hour pays for itself.

  1. 01read

    Start with the first-priority list

    The engineering practices open with an index you can filter by priority. The first-priority items are the ones a quality gate does not exist without.

  2. 02audit

    Walk one theme through your codebase

    Pick the theme closest to your last incident and check each technique against your repository. Every one names the thing to build and the mistake it replaces.

  3. 03enforce

    Turn the first repeated correction into a check

    When you give the same review comment twice, encode it as a lint rule, a type or a test. The practices name the mechanism for each rule.

Working with a coding agent? The practices are also served as plain Markdown at /resources/engineering-practices/llms.txt.

who they are for

Written for the people who own the outcome.

Engineering leads
A prioritized audit list for your own codebase, ordered so the first afternoon carries most of the value.
Teams adopting coding agents
Checks an agent cannot skip and rules the compiler enforces, so the work it hands back is verified before you review it.
Founders and buyers
A plain-language picture of what disciplined, agent-assisted engineering looks like, and what to ask of anyone who builds for you.

get in touch

Let's scope your project.

Tell us what you need and where things are stuck. You'll hear back within a day with a plain-language plan and a price. We skip the pitch deck and the discovery retainer.

Start a projectSee how we work