Field Notes
Opinions from the engagement, not from the conference circuit.
Short, opinionated essays on cloud architecture, production AI, and running serious technical programs. One diagram per essay. New posts every two to three weeks.
MethodJun 8, 2026Everything is code — even project management
A project-planning repo that sits alongside the code: ADRs, specs, tickets, transcripts, runbooks — all markdown, all in the IDE, all available to the AI working on the project.
Read note
InfrastructureJun 7, 2026The pipeline lives in the repo it deploys
Self-mutating deploy pipelines: the pipeline that builds a product is defined inside that product's own repository, and it updates itself before it ships your code.
Read note
ProgramsJun 6, 2026ADRs, not status decks
Running a multi-vendor government or enterprise program on architecture decision records and schedules built backwards from production cutover — instead of weekly status theater.
Read note
PracticeJun 5, 2026Senior on every engagement
Why we don't subcontract senior hours through staffing intermediaries — and what changes when the architect who scoped the work is the one who ships it.
Read note
AIJun 4, 2026The eval harness is the product
Production-grade AI is not a clever prompt. It's a system with evaluation, observability, caching, guardrails, and cost control designed in from day one.
Read note
CloudJun 3, 2026Audits that don't gather dust
A well-architected review is only worth what gets acted on. Cost models built before code, security and migration findings written as work you can ship — not a PDF that sits.
Read note- CloudJun 2, 2026
Cost before code
Why we build the cost model before we write the stack — and how pricing as a design input quietly changes the architecture you end up with.
Read note 
PracticeJun 1, 2026What we say no to (and why saying no is the service)
Three gates every engagement passes before we take it: it has to be expressible as code, it has to reach production in the window, and it has to be in our domain.
Read note