Josh Pollara

Describes multi-state transactions and how executing dependent states atomically can remove the need for external run-order orchestration like Terragrunt.

Explains the technical reasons for using OCaml for Stategraph: strong typing, immutability, type-safe SQL, and generated JSON serialization to ensure correctness for infrastructure state management.

An analysis of Terraform's global state locking, why a single-file lock doesn't scale, and how finer-grained graph-based coordination can reduce contention.

Discusses the velocity gap in modern engineering stacks, why Terraform's state system is a bottleneck, and how replacing the state substrate can unlock developer velocity without abandoning Terraform.

Argues that Terraform state is a distributed-systems problem best solved by modeling state as a graph with ACID transactions and subgraph isolation rather than flat files.

Explores ClickOps — GUI-driven infrastructure changes that generate HCL — and argues for preserving HCL as the source-of-truth while broadening who can create and modify infrastructure safely.