Field Notes · For evaluators & engineers
How we actually build the things we sell.
The credibility layer: engineering writing on the decisions behind software that lasts — architecture, testing, why we document everything, and how we hand work off so you own it. Written for the technical evaluator on your side of the table, and for the engineers we hope to work with.
The feed
What is published right now.
Performance budgets that fail the build, not the launch
A budget you only check at launch is a postmortem waiting to happen. The discipline that keeps a fast site fast is making the build itself refuse to regress.
ArchitectureWe treat content like code — and the CI proves the words too
Most sites let their copy float free of the system that renders it, so it drifts and rots. Modelling content as typed data puts the words under the same guarantees as the code.
ProcessWhat “you own your software” means in practice
Ownership is not a line in a contract. It is whether a different team could pick up your system tomorrow and run it without you — and that is something you can actually test for.
What Field Notes are for
Show the work, at the level an engineer would respect.
Most agencies are all marketing gloss with nothing technical underneath. Field Notes are the opposite — substantive, specific, never gratuitously academic. They demonstrate how we think about systems, which is the real product, and over time they earn the links and respect that lift the whole domain.
What we will write about
Three threads.
The engineering topics that decide whether software lasts — written from real decisions, not abstractions.
The threads
- Engineering
- Testing, reliability, performance budgets, and the discipline that keeps software working after launch.
- Architecture
- The decisions that make a system scale with the business instead of being thrown away when it grows.
- Process
- Why we document everything, how we scope and hand off, and what "you own your software" really means.
In the meantime
The proof you can inspect today.
How we build
The full engineering process, end to end — every stage with a deliverable you can hold.
Our principles
The few engineering principles we will not trade away — including telling you when not to build.
Custom Software
Where this rigor shows up most — software built around how you actually work, and owned by you.
Vetting us for a serious build?
The writing is one signal; a conversation is a better one. Talk to the engineers who would actually build it — no sales gatekeeper, a reply within one business day.