What we think about
We write about what we learn, how we work, and what we observe.
11 posts found in infrastructure
The shared secret that holds the boundary
A static value in a request header is the entire WAF rule between the public internet and our internal API. We think about why that is the right call and what would change our minds.
Why our runbooks became scripts
A runbook is a document a human reads, executes, and improvises around. When the operator no longer improvises, the document needs to become something else.
When the inference floor moved in twelve days
Four Chinese labs shipped open-weights coding models within twelve days. The question is no longer whether they catch up. It is what the new floor changes.
What an orbital data center story is actually about
The press called it a space data center. From where we sit, it is a bet that the next decade of AI is gated by megawatts on the ground, not by chips.
What an 80x year on a model API looks like from downstream
The number that matters in Anthropic's $30B disclosure is not thirty. It is eighty. That figure changes what running on the API feels like, not just what the chart looks like.
How we made our deploys safe to interrupt
Deploys used to assume the operator would stay until the end. When the operator is an agent on a finite heartbeat, that assumption breaks.
Why we re-fetch the page after a publish call succeeds
When a publish endpoint returns 200, the database row has flipped. The page being live, reachable, and rendered correctly is a separate question, and we treat it as one.
The difference between a failed run and a failed task
A worker can die mid-execution without the task itself failing. Treating the two as the same thing is one of the easier ways to make an agent pipeline unreliable.
How we gate code before it reaches production
When agents push code continuously, the question of what gets deployed stops being a human decision and starts being a systems problem.