Correctness & Foundations
Browse series · RSS · Atom
Start here: first entry.
Protocol State Machines: Invariants, Events, and Recovery
Design memo (January 2016): Protocol State Machines: Invariants, Events, and Recovery.
Idempotency Everywhere: Designing Safe Retries in Distributed APIs
Correctness-focused deep dive (February 2016): Idempotency Everywhere: Designing Safe Retries in Distributed APIs.
Backpressure as a Correctness Property: Stability Under Load
Design memo (March 2016): Backpressure as a Correctness Property: Stability Under Load.
Time Is a Lie: Clocks, Causality, and Ordering
Adversarial-first deep dive (April 2016): Time Is a Lie: Clocks, Causality, and Ordering.
Threat Modeling for Engineers: Assumptions as Interfaces
Correctness-focused deep dive (May 2016): Threat Modeling for Engineers: Assumptions as Interfaces.
Cryptographic Hygiene: Domain Separation, KDFs, and Context Binding
Threat-model-first analysis (June 2016): Cryptographic Hygiene: Domain Separation, KDFs, and Context Binding.
Crash Consistency: Durable State Without Mysticism
Engineering notebook entry (July 2016): Crash Consistency: Durable State Without Mysticism.
Memory Models and Concurrency: Reasoning About Races
Threat-model-first analysis (August 2016): Memory Models and Concurrency: Reasoning About Races.
Fault Injection: Turning Unknown Unknowns into Test Cases
Spec-driven research note (September 2016): Fault Injection: Turning Unknown Unknowns into Test Cases.
Observability as Specification: SLOs, Error Budgets, and Contracts
Design memo (October 2016): Observability as Specification: SLOs, Error Budgets, and Contracts.
Reproducible Builds: Trusting Artifacts in a Hostile World
Threat-model-first analysis (November 2016): Reproducible Builds: Trusting Artifacts in a Hostile World.
Security vs Reliability: When the Same Bug Has Two Names
Correctness-focused deep dive (December 2016): Security vs Reliability: When the Same Bug Has Two Names.