Series
Encode the System
An arc moving from manifesto toward conclusion: programming is not merely writing code, it is encoding guarantees into systems.
3 of 7 articles available
The series
Build Systems, Don't Polish Prose
We still talk about code as if it were style. But code runs in the world.
Why the implicit becomes fragile when humans and agents co-produce code.
Make Feedback Loops Attribute, Don't Just Detect
Why feedback loops become more powerful when code makes its system concepts explicit.
Enforce Architecture, Don't Trust Intent
Why load-bearing architecture rules must become executable checks rather than trusted intent.
Build Guarantees, Don't Chase Bugs
Why the goal is not fixing bugs faster but encoding guarantees that make whole classes of bugs impossible, rare, or visible.
Structure Domain, Don't Scatter Rules
Why domain invariants belong in domain structures, not in rules scattered across code paths.
Encode Guarantees, Don't Just Write Code
Programming is the art of deciding which truths to make unbreakable, where, and at what cost.
Series glossary
Forty concepts used across the published essays. Each definition describes what the term means inside this series.
- Abstraction
A representation that hides some details so attention can remain on the concepts that matter.
Central in article 2- Adapter
A thin layer translating between an external technology and the model or contract used by the system.
Central in articles 2, 3- Architectural fitness function
An automated check that continuously evaluates whether a system still satisfies an architectural property.
Central in article 3- Attribution
Identifying which rule, state, boundary, or responsibility produced the problem.
Central in article 3- Authority
The part of the system allowed to decide or perform an operation.
Central in article 1- Black-box test
A test that verifies observable behavior without depending on internal implementation details.
Central in article 3- Boundary
A point separating zones with different responsibilities, levels of trust, or kinds of behavior.
Central in articles 1, 2, 3- Cognitive portability
The ability to recognize the same conceptual structure across different languages, frameworks, or implementations.
Central in article 2- Colocation
Placing related pieces of code near one another, even when they belong to different runtime or architectural zones.
Central in article 2- Contract
An explicit statement of what may enter or leave a boundary and what each side guarantees.
Central in articles 1, 3- Correlation ID
An identifier used to connect logs, events, and calls belonging to the same operation.
Central in articles 1, 3- Detection
Establishing that something is wrong.
Central in article 3- Deterministic transformation
A transformation that always produces the same result from the same explicit inputs.
Central in article 1- Discriminated union
A type representing a finite set of alternatives, each identified by a common distinguishing field.
Central in articles 2, 3- Disposition matrix
A complete table classifying the meaning of every event in every possible state.
Central in article 3- Domain event
A named record that something meaningful happened in the domain or system model.
Central in article 3- Drift
The gradual divergence of code or behavior from the structure the system was intended to preserve.
Central in articles 2, 3- Exhaustiveness
A guarantee that every possible case has been considered and handled.
Central in articles 1, 3- Explicit
A concept represented in a visible, named, and inspectable form.
Central in articles 2, 3- Explicit state
A named situation the system can occupy, represented directly rather than inferred from scattered conditions.
Central in articles 1, 2, 3- Feedback loop
A mechanism that observes the result of a change and returns information that guides the next correction.
Central in article 3- Idempotency
The property that repeating the same operation does not produce additional unintended effects.
Central in article 1- Implicit
Information required to understand the system but not directly represented in the code being read.
Central in articles 2, 3- Invariant
A condition that must remain true throughout the relevant life of the system.
Example: A paid order cannot return to the pending-payment state.
Central in articles 1, 3- Invisible dependency
Knowledge on which the code depends even though that dependency is not represented or enforced.
Central in article 2- Local feedback
Fast checks concerned with the code immediately being changed, such as types, compilation, and nearby tests.
Central in article 3- Observability
The ability to reconstruct what a running system did, in which context, and why.
Central in articles 1, 3- Probabilistic machine
A system that generates likely outputs rather than following one uniquely determined continuation.
Central in article 2- Production-like feedback
Checks of critical behavior under conditions resembling real execution.
Central in article 3- Property-based testing
A testing approach that verifies general properties across many automatically generated inputs instead of relying only on manually selected examples.
Central in article 3- Pure function
A function whose result depends only on its inputs and which does not modify external state.
Central in articles 1, 3- Responsibility
The part of the system responsible for ensuring that an operation is accomplished.
Central in articles 1, 2, 3- Robustness
The capacity of a system to remain understandable, withstand deviations, and reveal what happens when it runs.
Central in article 1- Side effect
An interaction with something outside a local computation, such as a database, network, file, clock, or device.
Central in articles 1, 2- Snapshot
An immutable representation of the system state at a particular moment.
Central in article 2- State machine
A model that names possible states, accepted events, and allowed transitions between them.
Central in articles 1, 2, 3- Structural feedback
Checks that verify whether architectural boundaries, dependencies, and responsibilities still hold.
Central in article 3- Trace
A connected record of the steps taken by an operation across the system.
Central in articles 1, 3- Verification surface
The explicit forms in a system that tools and reviewers can inspect and check.
Central in article 3- ViewModel
A representation prepared for a user interface that exposes the state and actions the view needs without embedding domain behavior in the view.
Central in article 2